> On 20.10.2011 05:10, Jim Jozwiak wrote: > > Albrecht, > > > > Thank you so much for your patch and suggestions. > > You're welcome, I'm glad I could help you. > > > Did you also correct your code, or did you try with > the old code? >
Unfortunately, although your patch kept the app from hanging, it caused problems when the previous pulldown menu from the previous food had more menu items than the current pulldown menu from the current food--then there was garbage in the extra slots. Nevertheless, I am very grateful that you took the time and effort to install my program, look at the problem and then fix fltk. I appreciate the difficulty of decoding a novice's attempt to use fltk. This is why I am trying to create an simple example of the next bug I found. If I make all the packs and windows in NUT resizable, recompile, execute, and then show a tooltip (especially on NUT's "Options" tab), most of the widgets on the screen stop responding to clicks, and if a menu button still works, the pulldown menu's coordinates are shifted toward where the tooltip was. NUT has so many zillion packs and wizards within each other that I have not found exactly what is causing the problem so as to be able to create a simple test case. If you or anyone has a suggestion where to look, I would appreciate it. The NUT code I am using as a base is at http://www.lafn.org/~av832/newnut-17.2.tar.gz . My current theory is that when all widgets are resizable, the redraw after the tooltip (not specific to a single widget or necessarily a single group because a tooltip plops down however big it needs to be) somehow leaves fltk's view of screen coordinates corrupted. Jim _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
