Andreas Ekstrand wrote: > I don't set any when() condition on my buttons and I don't have any callback > on them. Instead, they are implemented as a button class of my own, derived > from Fl_Button, with a special handle method. The event causing the call to > clear() is a middle mouse button FL_PUSH, so that's already the case.
Okay, then you should only take care that you don't access the widget itself after calling clear(). Meanwhile I checked in the modified callback checks, so that you don't need the recently attached patches. Please use current svn or at least rev. 7115. > However, I can't test the latest code here because another widget crashes in > Fl_Browser_::draw() -> ... -> Fl_Browser::item_select. I have no idea why > but I will try to rebuild everything from scratch. That's strange. I hope that my recent changes didn't trigger this. If you can't find a bug in your application, then it would help if you can post a backtrace (gdb: bt) from after the crash. > If I can break away from that problem, would it make sense to change the > middle mouse button event causing the clear() from FL_PUSH to FL_RELEASE? No, I suspect that wouldn't help much. But if you can change it easily, I'd appreciate your test results with _both_ versions. This is just to get more data to analyze the fl_fix_focus event sending problem. It would probably be a great help for me to debug the problem, because your environment is different than mine. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
