Thank you to everyone who responded.  The problem is solved.  I'm embarassed to 
say that I mis-stated the problem.

My parent window wasn't getting the event at all.  I _thought_ it was, because 
originally the parent window was the only widget that made an "invalid 
keypress" buzzer noise - the super-window that all other widgets are added to, 
and therefore it should get all unhandled FL_PUSH events.

Anyway, somebody added another widget that also made the "invalid keypress"  
buzzer noise.  And that widget had overrides of show and hide and the bug was 
that the overrides were not calling their parent class (FL_Group::) show & 
hide.  So the hide wasn't happening correctly, even though visually the widgets 
were not there.

All this became much easier to figure out when I realized who was getting those 
events.

>
>
> > This all used to work -- I'm about to start backing out code.=20
> >  But any less drastic debug ideas would be appreciated.
>
>
> This sounds like the sort of thing you could try on a regular PC
> standalone?
> Much easier to debug there than in the target...
>
> Other than that, I've made roughly similar keypads in the past, and it's
> pretty much just worked, so I don't know what to suggest...
>
> The underlying buttons are the right size? They haven't shrunk somehow
> (to the size of your "active pixles") but you can't see that they've
> shrunk because the bitmap obscures the actual button...?
>
>
>
>
>
> SELEX Sensors and Airborne Systems Limited
> Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex=
>  SS14 3EL
> A company registered in England & Wales.  Company no. 02426132
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to