| [ Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File ]
STR #1979
Application: | FLTK Library |
Status: | 5 - New |
Priority: | 4 - High, e.g. key functionality not working |
Scope: | 3 - Applies to all machines and operating systems |
Subsystem: | Unassigned |
Summary: | [with a hackish fix] fltk::PackedGroup::layout() keeps layout_damage() at return |
Version: | 2.0-feature |
Created By: | anton146 |
Assigned To: | Unassigned |
Fix Version: | Unassigned |
Update Notification: | |
Trouble Report Files:
[ Post File ]No files
Trouble Report Comments:
[ Post Text ]
|
#1 | anton146 17:45 Jun 12, 2008 |
| 1) if you place an assert(!layout_damage()) to the end of the function. it fails even with test/pack 2) the current version of layout() at least to me seems to be too magical to be working(why exactly 2 iterations?) 3) ATM I've solved it with adding if(layout_damage()){ Group::layout(); layout_damage(0); } to the end of the function
offtopic: it came to me in a very hard reproducible bug in my app, as lagging menus. after some 5-6 hours of playing with it, I've noticed that PackedGroup::layout() was called ~1000 times more than when it doesn't lag | |
|
#2 | anton146 18:15 Jun 12, 2008 |
| oops, that broke it in other ways all right, I don't have any fix | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |