Create Executable ask before overwrite existing file

[Fredi]

When use "Create Executable" if a file with selected file name exist in output folder then file is replaced without any confirm. Today i lost important file

Please add a question when replacing files, or add an option in PB for enable or disable that.

Thank you.

[PB]

> Today i lost important file

But you always back up your important files, right?

[Fredi]

Not from this file unfortunately

[Kaeru Gaman]

I think that there is no requester is for a good reason...

when you compile a project and discover late bugs or do some final finetuning, it can be a nuisance to click away the requester again and again.

on the other hand, there is no good reason why you should call a completely new executable exactly the same name and compile it into the same directory.

and if you ever do so - shit happenes, should teach you to organize better.


so, my : AGAINST

[Fluid Byte]

+1

But only show the requester when you checked somthing like "overwrite executables silently" in the compiler options. No big deal, should added in a couple of minutes.

[Marlin]

I had a similar problem recently.

But I suggest a slightly different solution:

• - Disable the possibility to overwrite any file that is not an executable, like the ones PB would create.

Often you overwrite your old versions of the same PB executable,
that is not something you usually want to be warned about.

Besides, if you get used to acknowledge overwriting,
your not much safer than before.

If the file to be overwriten is not a PB executable, that [allmost(?)] allways means something that should not be done!

Such a thing would happen most easily, when you're playing a lot with some SaveFileRequester in your App,
that looks exactly like the one PB uses for creating executables and you start getting [a little] tired...

However a warning about overwriting PB executables that could be disabled
additionally to my suggestion would not be bad.