> Craig D wrote: > > Got a short example program, with pictures here: > > http://zenkinetic.com/fltktextbug.aspx > > 1 window, 1 TextEditor, 1 TextDisplay (the visible widget, completely > > covers the TextEditor), 2 buttons. > > Clicking in the TextDisplay causes the TextEdit to blast text on the > > TextDisplay. Covering and uncovering the window causes the TextEdtor to > > "take over". > > Hmm, I thought you were talking about overlapping > /windows/ which is fine, but not overlapping widgets.
I'm speechless, it has been so long since I've seen that restriction that I didn't even consider the possibity. My apologies if I didn't RTFM. > You appear to be trying to make overlapping widgets > both visible at the same time. As far as I know, > that's a big no-no. You are absolutely correct. I guess I would have considered this to be printed in big red blinking letters or that the toolkit would just say no. > Widgets shouldn't overlap unless only one is show() > and the rest are hide(). Does this mean that I can't have something like an animated backdrop with widgets on top? For example a video screen with controls as widgets or screen in screen? > I'd say offhand, change your callback handlers to something > that ensures when one widget is shown(), the other is hide(), Your suggestion works fine. > window.redraw(); // might not be needed Doesn't seem to be. > Also: what language is your example code written in? > This group is fairly C++ oriented, so code in other languages > will be lost on most of the folks here. zkl. A language I wrote and needed a graphics toolkit to graft on. Since, in this case, the code reads almost identical to the equivalent C++, I hoping it would be pretty straight forward for people who know FLTK code. Which you obviously do. Thank you for your help, I didn't grasp a fundamental concept. I think this explain some of the other problems I've been having. Craig _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
