windowstate chaos
Original Reporter info from Mantis: BeniBela @benibela
-
Reporter name: Benito van der Zander
Original Reporter info from Mantis: BeniBela @benibela
- Reporter name: Benito van der Zander
Description:
Changing the windowstate to wsNormal
Additional information:
When a normal form is minimized and the windowsstate is changed afterwards:
When setting windowsstate := wsNormal, the onwindowstatechange event is not called, but the form becomes visible. (This is the only good case of the four)
When setting windowsstate := wsMaximized: reading windowsstate immediately after the assignment returns wsMaximized, but then the onwindowstatechange event is called and reading the windowsstate propery there, returns wsMinimized. And the form remains minimized.
Once I manually open the window, onwindowstatechange is called again and windowsstate reads as wsMaximized.
---------------
When a maximized form is minimized and the windowsstate is changed afterwards:
When setting windowsstate := wsNormal: immediately after setting it, it has the value wsNormal, but then the onwindowstatechange event is called and the windowsstate property is again wsMinimized. Then the event is automatically called a second time, and now windowsstate = wsNormal is true. And the form becomes visible.
When setting windowstate := wsMaximized, absolutely nothing happens (although the value of windowstate becomes wsMaximized).
=============================
Expected behaviour:
When setting windowsstate := X on minimized form, the form should become visible. And the onwindowstatechange event should either be called or not, but if it is called, the windowsstate property should contain the value X.
(Window manager: gdm)
Mantis conversion info:
- Mantis ID: 18511
- OS: debian
- OS Build: squeeze
- Build: squeeze
- Platform: amd64
- Version: 0.9.31 (SVN)
- Monitored by: » sandro.cumerlato (Sandro Cumerlato), » januszt29@interia.pl (Janusz Tomczak)