| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #475
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Make changed() behave the same way with all FLTK widgets |
|---|
| Version: | 1.1.5rc1 |
|---|
| Created By: | mike |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1.5rc2 |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | mike
07:19 Jul 26, 2004 |
| Ariock mentioned on the fltk.general group that Fl_Choice is clearing the changed() flag before calling the callback, which is different from some other widgets.
Do an audit of the existing widgets and make the behavior consistent.
| |
| |
| #2 | mike
09:00 Jul 27, 2004 |
| OK, it wasn't consistent at all, but I changed all of the core widgets to set changed() whenever a value was changed regardless of the callback; the change state is cleared if we call anything other than the default callback function. | |
| |
| #3 | mike
09:00 Jul 27, 2004 |
| Fixed in CVS - the anonymous CVS repository will be updated at midnight PST. | |
[ Return to Bugs & Features ]
|
| |
