Re: Question about "the screen" property of stacks...

2019-07-12 Thread Bob Sneidar via use-livecode
Thanks Mark. I was playing with this to try and determine how to get a stack window to move to a position where it is fully visible on the screen it belongs to. Turns out not to be trivial, at least not for me. I worked out the math, and was feeling pretty proud of myself, until I realized the p

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Mark Waddingham via use-livecode
On 2019-07-11 19:30, Paul Dupuis via use-livecode wrote: Sorry, one more question: I assume since 'the screen of stack' is calculated dynamically, that in a 'on desktopChanged' handler (triggered by a monitor being removed) that looking at 'the screen of stack' for a stack on the now-removed mon

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Paul Dupuis via use-livecode
Sorry, one more question: I assume since 'the screen of stack' is calculated dynamically, that in a 'on desktopChanged' handler (triggered by a monitor being removed) that looking at 'the screen of stack' for a stack on the now-removed monitor would give you the closest remaining monitor? O

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Paul Dupuis via use-livecode
Thank you Mark! I will create an abbreviated summary for the Dictionary entry. I can now see why the programmer will get a  screen number for the stack even if the stack is not "on" any actually monitor (use loc to screenLoc line calculation), which is actually very helpful. Our application ha

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Mark Waddingham via use-livecode
On 2019-07-11 17:17, Paul Dupuis via use-livecode wrote: The screen of stack X returns the number of the monitor (the line number for the screenRects) that the stack/window is on. If someone from the mothership can verify, I would be happy to open a doc bug, update the dictionary, and generate

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Bob Sneidar via use-livecode
It was easy enough to test. It is the loc of the stack. I would have thought the top left, but that's just me. There's good reasons for both, but I am thinking like a Mac user. The window controls for Windows are topright! Bob S > On Jul 11, 2019, at 09:27 , Paul Dupuis via use-livecode > w

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Paul Dupuis via use-livecode
But is the number accurate? If so, I presume it is just comparing the saved loc of the stack to the screenRects, but what if the saved loc is not in any of the screenRects, then what does 'the screen of stack' return? 1 by default? or something else? I could, of course, but a second monitor,

Re: Question about "the screen" property of stacks...

2019-07-11 Thread Bob Sneidar via use-livecode
Curiously, it also returns the screen number for stacks that are not open. Bob S > On Jul 11, 2019, at 08:17 , Paul Dupuis via use-livecode > wrote: > > The screen of stack X returns the number of the monitor (the line number for > the screenRects) that the stack/window is on. > > How exac

Question about "the screen" property of stacks...

2019-07-11 Thread Paul Dupuis via use-livecode
The screen of stack X returns the number of the monitor (the line number for the screenRects) that the stack/window is on. How exactly is this determined? I presume it is based on the loc (location) property of the stack, since the window (effective rect or rect) itself can span multiple monit