http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1237
ulf.lamping@xxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Major |Enhancement
------- Comment #1 from ulf.lamping@xxxxxx 2006-11-22 22:48 GMT -------
Well, first of all, thanks for this detailed report - it makes it clear what
you're thinking about.
The current (intended) implementation is based on the preference setting:
- open/save dialogs use the last used dir (default) or
- open/save dialogs use a fixed directoy
So you're asking about to let WS use the current working dir for initial
open/save dialogs - that's an enhancement and not a bug (I've changed it that
way).
However, your report makes some assumptions that are not quite right in a lot
of cases.
First of all, a lot of GUI based user don't even know what a cwd is. They start
Wireshark with the GUIs menu entry (be it on Windows, KDE, GNOME ...) - in this
case the cwd often just doesn't make a lot of sense - or even worse points to
the program directory where the user doesn't have write access to.
Secondly, a lot of users I talked to saved their capture files in a special
directory (which can be easily quite huge) and want to use this directoy for
all open/save operations.
So basically what your asking for is a third option to use the cwd. That would
be a third option for the file dialog preference and certainly *not* the
default.
I don't know if any of the developers will implement this - and to be honest I
don't know if this should be implemented at all. Having to navigate to a
current working dir to let the open/save dialog be in the right dir seems to be
an odd way to work with a GUI program.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
