Anonymous | Login | 12-12-2019 13:02 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0001468 | [tweak] Any | trivial | always | 07-15-05 01:32 | 07-15-05 02:31 | |||||||
Reporter | elenzil | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | |||||||||
Status | new | |||||||||||
Summary | 0001468: filedialog - multiple InvalidDirectoryErrors when we should get only one or none, imo. | |||||||||||
Description |
when initializing a filedialog with an invalid directory, the user gets the following aptly-titled dialog: "An problem has occured: InvalidDirectoryError" [sic]. .. Which is possibly reasonable, altho personally i would prefer not to be notified of that and just have the browser choose either the current directory or the root directory as default. However, the error dialog must be "Abort"ed three times before it finally goes away and all is finally well with the world. Why are you initializing a dialog with an invalid directory you ask ? Well, our app keeps track of a 'user's last directory' so that the filebrowser opens up in a convenient spot. We then use the app to load a default scene, say, and save the resulting squeak image. We then pass that .image on to a user, who possibly installs it in a different location. True, we should check the directory before trying to browse it, but since we're obviously going to choose some default directory, i think the file browser could just do that rather than sending up scary-looking errors in triplicate. |
|||||||||||
Additional Information | ||||||||||||
Attached Files | ||||||||||||
|
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
44 total queries executed. 33 unique queries executed. |