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

Paul Dupuis paul at researchware.com
Thu Jul 11 12:27:15 EDT 2019


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, and create a test stack to 
determine all this, but some one at LiveCode should know (or be able to 
tell from the code) and then, as I said, I will add it to the Dictionary 
entry.


On 7/11/2019 11:25 AM, Bob Sneidar via use-livecode wrote:
> 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 <use-livecode at lists.runrev.com> 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 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 monitors, but the loc of a stack, being a point, must be one only a single monitor.
>>
>> However, if someone with applicable knowledge could confirm that it would be appreciated. The Dictionary does not clarify how the screen is determined.
>>
>> It would also help if someone could confirm that the screen value is meaningless until the stack/window is opened (much like that the effective rect is meaningless until a stack is opened)?
>>
>> If someone from the mothership can verify, I would be happy to open a doc bug, update the dictionary, and generate a PR for an update to the screen property Dictionary entry to clarify these two points.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>





More information about the Use-livecode mailing list