Feature Request: File/Directory Unlocking

Post by **nikos** » 2005 Aug 16, 12:56

you either have to live with delete errors or without "current directory", sorry

bright · Post by **bright** » 2005 Aug 23, 10:24

nikos wrote:you either have to live with delete errors or without "current directory", sorry

How difficult can it be for a program to just remove the lock when the exact same program tries to delete something?

Also, even when we should live with it (which is bloody nonsense!!) why does the program try to delete something that it has locked by itself anyway? In thata case, it should not have to wait for the timeout on replying to the user that the folder is locked.

The message to the user should be this:

'I'm sorry, I cannot delete this folder because I am using it without doing anything with it. Please, make sure I am not using this folder when you ask me to delete it!'

bright · Post by **bright** » 2005 Aug 23, 10:26

btw: I'm a computer programmer too, knowing many of the usual problems someone can get trying something...

Please, try to read some sources dealing with user interface!

MKairys · Post by **MKairys** » 2005 Aug 23, 11:54

Perhaps you should read some sources dealing with politeness.

Gandolf · Post by **Gandolf** » 2005 Aug 23, 12:33

bright wrote:I'm a computer programmer too, knowing many of the usual problems someone can get trying something...

Please, try to read some sources dealing with user interface!

Perhaps you should show us some of your programs and let us see your PERFECT user interface.

bright · Post by **bright** » 2005 Aug 23, 12:40

Better not

And I do not mean to be unpolite. 'Please' was typed in there for a purpose, you know.

There are plenty of 'mistakes' in the user interface of my programs too - everyone makes them. But, at least, I try to correct them without saying the user must be wrong because he/she uses the program somewhat other than I was thinking of.

Post by **nikos** » 2005 Aug 23, 12:49

i have said many times in the past that this "locking" could affect so many parts of the UI that it may take me ages to fix. (e.g. what if after x2 "unlocks" the user cancels the delete? and myriad other such issues)

For users that only come across this situation infrequently (e.g. i never do) it isn't much of an issue since they can take care to unlock it themselves by browsing another folder

if you find that this occurs too often and it slows you down and the workaround i offered won't work, and you can't appreciate the remaining features of the program, then clearly x2 isn't for you

i work with limited resources and this particular bug/feature is very low in my priority list

bright · Post by **bright** » 2005 Aug 23, 13:00

That's a pity, however, I understand your priority problems.

Maybe at least changing the current pointer to the currently browsed folder when a script is run, even when the browsed folder is not locked?

Post by **nikos** » 2005 Aug 23, 13:32

you can do that already by making your scripts "multiline"
say that you want to execute a script that deletes the selection or something. Instead of issueing just the delete command, have two, the first one doing the CD: (notice the comma)

Code: Select all

cd "$P" , del "$N"

(use the preview button if you can't understand what this does)

actually you are CD-ing way too many times but this won't affect the operation

ps another possibility is to use $-tokens that correspond to full paths, e.g. $F instead of $N. Then you don't need the current directory either