+[8.50ß6 x64] minimize during copy with keyboard wrong

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
Laszlo
Junior Member
Junior Member
Posts: 93
Joined: 2011-09-17, 07:27 UTC
Location: Hungary

+[8.50ß6 x64] minimize during copy with keyboard wrong

Post by *Laszlo »

So, If i minimize total commander during copy with mouse with the _ button, it goes to taskbar, showing percent, progress bar, etc. But if I use windows key + down arrow, it minimizes only the "copying window", leaving the total commander window visible. But only during copy.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48088
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I can confirm the problem. Unfortunately it seems that Windows doesn't send a WM_SYSCOMMAND with SC_MINIMIZE when you press Windows+Down, but somehow minimizes the window by itself. Therefore TC cannot react to it. Any idea what is going on here?
Author of Total Commander
https://www.ghisler.com
Laszlo
Junior Member
Junior Member
Posts: 93
Joined: 2011-09-17, 07:27 UTC
Location: Hungary

Post by *Laszlo »

I see, it is a Windows issue, sorry!
gdpr deleted 6
Power Member
Power Member
Posts: 872
Joined: 2013-09-04, 14:07 UTC

Post by *gdpr deleted 6 »

@ghisler:
Just FYI, in case you might want to consider this in a future release.

Windows+DownArrow and other Windows key shortcuts cause a WM_SIZE message being sent, telling in wParam whether the window has been SIZE_MINIMIZED, SIZE_MAXIMIZED or SIZE_RESTORED.

Note that WM_SYSCOMMAND + SC_MINIMIZE/SC_MAXIMIZE/SC_RESTORED will trigger a respective WM_SIZE message too, so WM_SIZE could be a drop-in replacement for those cases
(unless you need to know before the actual resize happens).

You might still want to keep the WM_SYSCOMMAND variant around for backwards compatibility with Win9x/NT, since WM_SIZE was only introduced with Windows 2000.

EDIT: As pointed out by @MarcinW in another thread, MSDN documentation doesn't mention Win9x/NT anymore, and (wrongly) states min. requirements being Win2000.
Now, i don't have such an old OS image lying around here, but a quick googling seems to indicate that WM_SIZE with those 3 parameters is indeed by Win9x/NT.
(Why does MS need to lie in their dev. documentation? It is not like it is being used as marketing material or such. Me angry... :x )
Last edited by gdpr deleted 6 on 2013-10-22, 19:40 UTC, edited 1 time in total.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48088
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Thanks, I will try to react to WM_SIZE!
Author of Total Commander
https://www.ghisler.com
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48088
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I'm handling WM_SIZE now in beta 7 - can you try it, please?
Author of Total Commander
https://www.ghisler.com
gdpr deleted 6
Power Member
Power Member
Posts: 872
Joined: 2013-09-04, 14:07 UTC

Post by *gdpr deleted 6 »

It works, thanks!
Tested with TC8.50b7 32-bit and 64-bit.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48088
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Great, thanks for testing!
Author of Total Commander
https://www.ghisler.com
Post Reply