| [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #879
Application: | FLTK Library |
Status: | 1 - Closed w/Resolution |
Priority: | 3 - Moderate, e.g. unable to compile the software |
Scope: | 2 - Specific to an operating system |
Subsystem: | FLUID |
Summary: | Fluid: New Input_Choice via menu, crash |
Version: | 1.1-current |
Created By: | Portale |
Assigned To: | matt |
Fix Version: | 1.1.7 (SVN: v4451) |
Update Notification: | |
Trouble Report Files:
No files
Trouble Report Comments:
|
#1 | Portale 23:59 May 22, 2005 |
| Adding a new Input_Choice by clicking on the Widget Bin in fluid works fine. But Adding it via "New->Menus->Input_Choice..." makes fluid crash.
Windows XP Visual Studio .NET
this is a duplicate of <http://www.fltk.org/str.php?L817> but with the corect fltk version. | |
|
#2 | Portale 15:12 Jun 07, 2005 |
| Debugging showed me that the reason for the crash may lie in "fl_type.h", Fl_Input_Choice_Type::textstuff(..). There, the fresh widget is taken from the factory and casted to a Fl_Menu_ pointer. And then the textsize() of that supposed Fl_Menu_ is set. Actually, the new widget from the factory is an Fl_Input_Choice, which has no textsize_ attribute. So, the textsize value is written somewhere into the Fl_Input_Choices memory (in my case into the first byte of the Fl_Input_Choice/FL_Groups resizable_ pointer). This makes it crash on Windows. On OSX, this doesn't seem to hurt.
I think Fl_Input_Choice_Type::textstuff(..) needs some adjustment, but don't know what it should do exactly. | |
|
#3 | matt 15:57 Jul 23, 2005 |
| Fixed in Subversion repository.
Fluid was casting Fl_Input_Choice to Fl_Menu_ which caused plenty of confusion, since Fl_Input_Choice is actually derived from Fl_Group. | |
[ Return to Bugs & Features ]
|
| |