Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#37 Why generate wxNullBitmap for bitmap buttons?

open
nobody
None
7
2012-07-13
2005-09-18
Joel Low
No

It's not only the bitmap buttons, but also the toolbar
buttons. Why not include a Disabled bitmap property and
use that bitmap instead of wxNullBitmap which has
some... bad UI outcomes.

I have tried to uncomment the line which tells the
property inspector to add a Disabled bitmap line, but
it all gets muddled up and the active bitmap becomes
the disabled bitmap.

Discussion

  • Logged In: NO

    All this is due to sheer laziness on my part :o( . When I
    started out with the intial design, I completly ignored the
    disabled icon implementation because I really havent used
    it. If we need to add Disabled bitmap, lot of things need to
    be revamped. The internal architecture of the bitmap
    handling code need to be completly revamped(whenever we try
    to manipulate a components bitmap, we directly
    manipulate/typecast the active ones alone).
    I guess an Interface should be implemented for items that
    handles active and inactive bitmaps.

    -Guru

     


Anonymous


Cancel   Add attachments