[Bug] File object

[Gustav]

Thought this bug was reported some days ago, but I don't found the Thread yet. Maybe I'm wrong...

If you're deleteing a file that is no existing, after that this one File object isn't able to delete other existing files.

[Yves]

It's the way the object works, although I don't remember why it was done like this : when an error occurs, the other actions don't work until the error is cleared. Just clear the error code (there is an action for that) before doing anything, that will solve the problem.

In a future version of this object we'll add an option to ignore the last error code.

[Gustav]

Thanks, that's okay.

[Sphax]

You can use too, the "File-Folder object" which is able to delete files in a fastloop and browse a folder and sub-folder in a File-Folder loop.

[Gustav]

I'm using it in the same application and don't know that. :crazy:

[Sphax]

If you ask your question about the file object because you want to empty a folder, you can also do that through one action with File-Folder object.

[Gustav]

I found an issue in the save selector.

If a file "File.txt" exists and I want to save with "File.txt" the selector ask me for confirmation. But when I want to save with "File" it don't ask me although the TXT-filter is selectet!? :confused: So this file would be overwritten! No other Windows selectors do so. Please fix it.

[Yves]

You probably forgot to set the default extension to ".txt" (action "File Selector / Set default extension"). I've just tested, it works fine, the message box is displayed even if you don't specify the extension.

[Gustav]

Oh my god ... You are right. -.-

I got paranoid by this object but this was my mistake. Thank you!


Edit

But it's odd... If I set the default extension to "X" it adds the selected extension in the selector.

[Gustav]

Okay, some cases:

settings
selector filters: "txt|*.txt|rtf|*.rtf"
[color:#660000]default extension: "" (nothing)[/color]
files x.txt and x.rtf exists

testing
selected [color:#000099]txt[/color] or [color:#000099]rtf[/color] filter + fileanme input [color:#000099]x[/color] = [color:#990000]no prompt[/color]
Get result pathname = [color:#000099]path\x[/color]
selected [color:#000099]txt[/color] or [color:#000099]rtf[/color] filter + fileanme input [color:#000099]x.txt[/color] or [color:#000099]x.rtf[/color] = [color:#990000]prompt[/color]
Get result pathname = [color:#000099]path\x.txt[/color] or [color:#000099]path\x.rtf[/color]

settings
selector filters: "txt|*.txt|rtf|*.rtf"
[color:#660000]default extension: "X"[/color]
files x.txt and x.rtf exists

testing
selected [color:#000099]txt[/color] or [color:#000099]rtf[/color] filter + fileanme input [color:#000099]x[/color] = [color:#990000]prompt[/color]
Get result pathname = [color:#000099]path\x.txt[/color] or [color:#000099]path\x.rtf[/color]
selected [color:#000099]txt[/color] or [color:#000099]rtf[/color] filter + fileanme input [color:#000099]x.txt[/color] or [color:#000099]x.rtf[/color] = [color:#990000]prompt[/color]
Get result pathname = [color:#000099]path\x.txt[/color] or [color:#000099]path\x.rtf[/color]


[color:#009900]-->[/color] What is the sense of the default extension?

[color:#009900]-->[/color] Regardless of that wouldn't it be better the file selector always tests for existing files with the actually selected filter if no extension were inputed after the filename?

Edit

(Or add a type variable "Always overwrite prompt" or something?)