Neil Hodgson wrote:
Philippe Lhoste:
> I found the behaviour a little strange. If there is no active
> directory properties file then the Open Directory Options File command
> opens one in the same directory as the current file. This is the most
> obvious behaviour but I normally expect that the file will go into a
> parent directory.
Sorry, but I don't understand the issue.
Say I don't have a directory properties file and am editing
"c:\os\scite\src\SciTEProps.cxx" so Open Directory Options File opens
"c:\os\scite\src\SciTEDirectory.properties" but really that makes no
sense since this is a leaf directory and so I could just edit local
properties. I probably mean to create
"c:\os\scite\SciTEDirectory.properties" or even
"c:\os\SciTEDirectory.properties" but there is no way to determine
which. It could default to the parent directory of the current file
(or only default there if the current directory is a leaf directory)
but there are benefits and problems either way.
OK, reading this then re-reading the initial description, I finally
understand (a bit thick sometime!). I didn't understood the issue was
with the Options menu, Open Directory Options File sub-menu!
I agree this is basically not logical, doing the same job as the Local
Option File.
But as you point out, it is difficult to find a good default behaviour.
Note that a leaf directory can be made later a parent directory, just by
creating a sub-dir...
I say we have perhaps two choices:
1) Keep current behaviour, as it is simple and user will know where the
file will be. Thereafter, he can move manually the file in the upper
directory of his choice.
2) Don't create a file but an unsaved buffer, asking where to save it,
ideally defaulting to the path of the current file at time of creation
(I don't know if this is possible or easy!).
3) If no file is found, just show a Save dialogue pointing to the
current directory (of current buffer). Then the user can just go up in
the dialogue and save before editing.
I know, that's three choices, I added 2) as an afterthought, but I think
I prefer the 3), even if it departs from the current behaviour of other
Option File commands: it even let the user the choice to cancel such
creation, if that wasn't what he wanted to do.
--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
