| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #1382
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 3 - Moderate, e.g. unable to compile the software |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | FLUID |
|---|
| Summary: | fluid: changing a menuitem shortcut does not make fluid think file needs to be saved |
|---|
| Version: | 1.1.7 |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | matt |
|---|
| Fix Version: | 1.1-current (SVN: v5328) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | greg.ercolano
17:44 Jul 31, 2006 |
| If I save the fluid file, then change the shortcut for a menu item then hit ^S (save), the .fl file is not saved.
Further, one can quit fluid without being warned changes were made, causing the change to be lost.
Fixes suggested:
o Changing a shortcut should mark the fluid file 'unsaved'
o If the user hits ^S and there's nothing to save, the user
is not told nothing was saved. In the case of this kind of bug,
the user thinks they saved something when nothing actually
happened. Maybe the solution is to post a dialog warning
the user no changes were made, so there's at least some
feedback no save occurred. | |
| |
| #2 | wilson.afn
18:03 Jul 31, 2006 |
| > o Changing a shortcut should mark the fluid file 'unsaved'
Amen on that.
> o [ ...Berate the user with a dialog to defend against further such bugs...]
-1 on that :) . Hopefully, FLUID can be made to do the Right Thing(tm) without these extreme measures. | |
| |
| #3 | matt
07:01 Aug 17, 2006 |
| Fixed in Subversion repository.
Please post if you find any more of these "modified" flag issues. I know of one more, but I am unsure if "fixing" those makes sense or is rather annoying: changing the selected widget will not mark the document dirty, even though this information *is* saved in the .fl file. | |
[ Return to Bugs & Features ]
|
| |
