TC 8 b12 x86 / Win7 x64 : Double info dialog box on deletion

wazzup · Post by *wazzup » 2011-12-12, 15:11 UTC

Hello

When the file cursor is on a 'goto parent dir' item (i.e. '..' item) without having selected files or dirs, the delete action through the delete key or F8 displays the 'No files selected!' information dialog box.

When the path is a fixed local hard drive, the information dialog is displayed twice.
This does not happen with USB drives, network paths (e.g. \\server\path) or mapped network paths (e.g. s: mapped to \\server\path)

TC 8 b12 x86 / Win7 x64

Best Regards

Flint · Post by *Flint » 2011-12-12, 15:27 UTC

Cannot reproduce here. Tested TC 8.0β12 x32, x64; Win7 x64 SP1.

wazzup · Post by *wazzup » 2011-12-12, 15:32 UTC

update:
This only happens when the setting 'Use Explorer delete method (faster, cannot handle comments)' is not enabled.

Best Regards

karlchen · Post by *karlchen » 2011-12-12, 16:28 UTC

Hello, wazzup.

Reported behaviour reproduced using Total Commander 8.0ß12 32-bit on Windows 7 Enterprise Edition SP1 32-bit.
Selected drive: local
T.C.: UseTrash=1, VistaDelete=1, Win95Delete=0
Win: Recycle bin: on, confirmation: on

Kind regards,
Karl

Post by *ghisler(Author) » 2011-12-14, 15:30 UTC

I can reproduce it with VistaDelete=1, thanks. What happens is that TC first tries VistaDelete, which fails, and then tries also normal delete (which also fails).

karlchen · Post by *karlchen » 2011-12-16, 17:00 UTC

Hello, Christian,

I cannot reproduce the double 'No files selected!' error message using Total Commander 8.0ß13 x32 / x64.
So the problem seems to have been solved.

Server 2008 R2
Total Commander 8.0ß13 x32
Total Commander 8.0ß13 x64

Kind regards,
Karl

Post by *ghisler(Author) » 2011-12-18, 15:50 UTC

Thanks! Can anyone confirm it?

karlchen · Post by *karlchen » 2012-01-15, 00:27 UTC

Hello, Christian.

Should this thread not be moved to the "Fixed Bugs" section? The reported problem has been fixed. The fix has been confirmed, even though not by the O.P. Yet, during the past few weeks no-one has reported the problem had re-appeared.

Kind regards,
Karl

Post by *ghisler(Author) » 2012-01-16, 15:28 UTC

Normally I move bug reports to the "Fixed" section if either
1. The original poster confirms the bugfix,
or
2. At least 2 other users confirm the fix,
or
3. If it's a very obvious fix.

So can anyone else confirm this fix?

umbra · Post by *umbra » 2012-01-16, 16:29 UTC

Hi, I can reproduce the bug in beta 12 but not in beta 16. So I confirm it's fixed.

Post by *ghisler(Author) » 2012-01-18, 15:23 UTC

Great, thanks a lot!