Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Mark Wieder via use-livecode
On 10/21/19 2:03 PM, Paul Dupuis via use-livecode wrote:  True. I just wrote a Win10 specific fix like the one Panos posted in the bug. Still I look forward to the day I can remove that and not have call a hrEffectiveRect function that returns 'the effective rect' for every OS except Windows

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Paul Dupuis via use-livecode
On 10/21/2019 4:41 PM, Richard Gaskin via use-livecode wrote: Paul Dupuis wrote: > When the 'effective rect' of a stack was introduced to provide the > outer boundaries of a stack, along with the effective working > screenRects(s), I rewrote all my complicated windows management code > (and

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Bob Sneidar via use-livecode
As have I. Bob S > On Oct 21, 2019, at 11:51 , Trevor DeVore via use-livecode > wrote: > > On Mon, Oct 21, 2019 at 1:31 PM Paul Dupuis via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> Add your name to this bug: >> https://quality.livecode.com/show_bug.cgi?id=16305 >> >>

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Bob Sneidar via use-livecode
I have fits with using these rects. It ought to be as simple as saving the rect of a stack when closing it, and restoring it when opening it, regardless of what monitor is in effect. My problem comes in when I run the stack in a 1080p monitor at work, sleep it then go into the field, now Im

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Richard Gaskin via use-livecode
Paul Dupuis wrote: > When the 'effective rect' of a stack was introduced to provide the > outer boundaries of a stack, along with the effective working > screenRects(s), I rewrote all my complicated windows management code > (and some of your clever tricks for Windows weirdness, Richard), to >

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Paul Dupuis via use-livecode
Thank your Richard and Trevor. When the 'effective rect' of a stack was introduced to provide the outer boundaries of a stack, along with the effective working screenRects(s), I rewrote all my complicated windows management code (and some of your clever tricks for Windows weirdness, Richard),

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Richard Gaskin via use-livecode
Paul Dupuis wrote: Add your name to this bug: https://quality.livecode.com/show_bug.cgi?id=16305 Mark Waddigham chimed in at one point that the Windows API returns the 8px border width under Windows 10 - the 1px visible border and a 7px "touch area" is apparently how Microsoft views it, so

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Trevor DeVore via use-livecode
On Mon, Oct 21, 2019 at 1:31 PM Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: > Add your name to this bug: > https://quality.livecode.com/show_bug.cgi?id=16305 > > Mark Waddigham chimed in at one point that the Windows API returns the > 8px border width under Windows 10 -

Re: Effective rect of stacks on Windows 10

2019-10-21 Thread Paul Dupuis via use-livecode
On 10/21/2019 2:11 PM, Trevor DeVore via use-livecode wrote: I am looking for input from people who are using `the effective rect of stack` and the values it reports on Windows. I have some code that uses the effective rect of a group to determine if the stack is still on the screen after the

Effective rect of stacks on Windows 10

2019-10-21 Thread Trevor DeVore via use-livecode
I am looking for input from people who are using `the effective rect of stack` and the values it reports on Windows. I have some code that uses the effective rect of a group to determine if the stack is still on the screen after the user moves the stack or when restoring window positions when an