Wish: Confirm question on Exit of TC

[Bluestar]

@wanderer:

No, TotalConfirmExit doesn't uses any plugins at all - it simply performs a WinAPI call to show a MessageBox after loading the appropriate language string(s) from the currently used "WCMD_*.LNG" file, and sends a close message (cm_Exit) to TC in case the user chooses "Yes" inside that modal dialog.

TC's internal "Redefine hotkey" feature is being used for the app to be called: it auto-registrates itself in "usercmd.ini" & "wincmd.ini" for the keys Alt+X and Alt+F4, so no other user interaction is needed.

[wanderer]

Nice. Thanks for the info. It seems pretty decent, so i'll try it.

[wanderer]

Since a specific post for TotalConfirmExit does not seem to exist in the plugins forum, i'll post a peculiarity of the utility here. When exiting and re-loading TC, TC's "X" (close window) button is re-enabled. If you press ALT+F4 once and the utility is executed then it disables that button. So it's not 100% safe...

Note (mainly to Christian): Perhaps TC could help a little here. If it's difficult to add the functionality directly to TC, perhaps an "ConfirmationEXEToBeExecutedWhenTCExits" ini entry can be added so when TC is to be closed (by any means), the confirmation EXE could be executed by TC itself.

[MVV]

My plugin works 100%. It simply subclasses window procedure and catches all close messages so there's no way to bypass it.

[wanderer]

My plugin works 100%. It simply subclasses window procedure and catches all close messages so there's no way to bypass it.

Right. It's always loaded.

I wonder though why is it so difficult to implement it in TC itself? I got the impression that when this issue was first discussed, the problem was bad timing. A new version of TC was near release and there was no time to add a confirmation string and alert the translators.

Christian, any comments???

[Sir_SiLvA]

I wonder though why is it so difficult to implement it in TC itself?

I dont think its hard to implement it its just an unneeded annoyance...
I personaly dont like Apps that upon clicking the X ask "are you sure you wanna do what you just clicked?".....

[wanderer]

I wonder though why is it so difficult to implement it in TC itself?

I dont think its hard to implement it its just an unneeded annoyance...
I personaly dont like Apps that upon clicking the X ask "are you sure you wanna do what you just clicked?".....

IMO the best solution would be for Christian to provide a ConfirmOnClose INI setting which would have the same values as MinimizeOnClose. That way the user would be able to configure TC as he sees fit. All i know is that I have pressed ALT+F4 instead of ALT + F3 too many times so far and as i'm getting older, things don't seem to improve .

[Perplexer]

I wonder though why is it so difficult to implement it in TC itself?

I dont think its hard to implement it its just an unneeded annoyance...
I personaly dont like Apps that upon clicking the X ask "are you sure you wanna do what you just clicked?".....

We are suggesting this feature as an option! You could go into Options and uncheck the "Ask before closing" and you would not see the confirmation window, ever. I on the other hand would have it checked and get the confirmation window. So how can that be an annoyance? It's really not.

[DrShark]

"Confirm exit" warning can be helpful in case if we have any of Commander's children windows, like file properties dialog, Lister or Find Files in separate mode also opened.

[MVV]

Especially when one of those properties windows is applying attributes to a lot of files... and closing TC will stop operation w/o confirmations.