Wimp_WindowGetState oddity?
Andrew Conroy (370) 740 posts |
With Wimp_WindowGetState, it should return the window’s location in the stack at offset 28, with -1 for top of the stack, -2 for bottom of the stack, -3 for iconised or a window handle for the window it is immediately behind. I can get -1 for the top of the stack, or a window handle if it isn’t top of the stack, but if I iconise the window I don’t get -3, I get another window handle. I must be misunderstanding something somewhere, what am I doing wrong? |
David Pitt (102) 743 posts |
That would be nice to know as I do not get -3 when the window is iconised either. ROOL’s PRM on Windows Locations has -3 meaning “iconized (not visible)”. What does “not visible” infer, the window contents are not visible but the pinned icon is. My paper PRM under Wimp_OpenWindow has -3 "means to open the window behind the Wimp’s backwindow, hiding it from sight. Does that mean iconising? Hmm!! |
edwardx (1628) 37 posts |
I think the use of -3 only applies to Wimp_OpenWindow. If you want to detect when your windows are iconised, check if the handle at offset 28 is -3 when the wimp sends you an open window request.
Not quite. If you just open your window behind -3 then the pinboard won’t know about it. If you broadcast Message_Iconize the pinboard will send you an open window request with -3 at offset 28. |
Andrew Conroy (370) 740 posts |
According to the documentation here it applies to Wimp_GetWindowState too, I think, unless I’m misunderstanding it. |
David Pitt (102) 743 posts |
I am coming to the view that edwardx is correct and the ROOL online PRM entry for This from the paper and PDF PRM for R1+28 handle of window in front of this one (or –1 if none) Unless someone knows otherwise that is. If not I can edit the wiki. |