+[8.50ß6 x64] minimize during copy with keyboard wrong
Moderators: Hacker, petermad, Stefan2, white
+[8.50ß6 x64] minimize during copy with keyboard wrong
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.
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
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
https://www.ghisler.com
-
- Power Member
- Posts: 872
- Joined: 2013-09-04, 14:07 UTC
@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...
)
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...

Last edited by gdpr deleted 6 on 2013-10-22, 19:40 UTC, edited 1 time in total.
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I'm handling WM_SIZE now in beta 7 - can you try it, please?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
-
- Power Member
- Posts: 872
- Joined: 2013-09-04, 14:07 UTC
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact: