0001468: filedialog - multiple InvalidDirectoryErrors when we should get only one or none, imo.

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

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

Relationships

Notes
(0001803 - 220 - 322 - 322 - 322 - 322 - 322) andreas 07-15-05 02:11	A very simple solution to this problem is to add a line saying: lastUsedDirectory exist ifFalse:[lastUsedDirectory := FileDirectory default]. and only then: fileDialog directory: lastUsedDirectory.

(0001804 - 139 - 163 - 163 - 163 - 163 - 163) elenzil 07-15-05 02:18	thanks andreas. i agree, i just think that functionality should be in the dialog, with perhaps one notification if the problem occurs.

(0001806 - 126 - 126 - 126 - 126 - 126 - 126) andreas 07-15-05 02:28	Yes I agree, something needs to be done here but I was just trying to be helpful and offer a workaround for the short term ;-)

(0001807 - 14 - 14 - 14 - 14 - 14 - 14) elenzil 07-15-05 02:31	roger, thanks!

Issue History
Date Modified	Username	Field	Change
07-15-05 01:32	elenzil	New Issue
07-15-05 02:11	andreas	Note Added: 0001803
07-15-05 02:18	elenzil	Note Added: 0001804
07-15-05 02:28	andreas	Note Added: 0001806
07-15-05 02:31	elenzil	Note Added: 0001807

Mantis 1.0.8[^]

44 total queries executed.
33 unique queries executed.