On Mon, Jan 11, 2016 at 4:03 PM, Bob Sneidar
wrote:
> There is no notion of a current screen in the OS itself. Do you mean which
> screen the frontmost window is in? And what do you mean by "In"? A window
> can overlap two or more screens. Typically if you double click the title
> bar of a window
works in 6.7.6
> On Jan 9, 2016, at 18:20 , Monte Goulding wrote:
>
>
>> On 10 Jan 2016, at 10:55 am, Dr. Hawkins wrote:
>>
>> As I look through screenLoc, screenRect(s), etc., I'm not seeing *any* way
>> to figure out which screen an object is on, short of manually comparing
>> elements of i
There is no notion of a current screen in the OS itself. Do you mean which
screen the frontmost window is in? And what do you mean by "In"? A window can
overlap two or more screens. Typically if you double click the title bar of a
window, the window will maximize on the screen the mouse is in.
We get Split View for free if we implement fullscreen. I was going to do it for
Hacktoberfest but it was interesting working out the syntax and how it
interacts with the current fullscreen property and decorations so I went for
something simpler instead.
Cheers
Monte
Sent from my iPhone
> On
It's really hard to say how all the advices to this question apply to the new
feature of "SplitView" of OSX 10.11 (https://support.apple.com/en-ca/HT204948)
Luckily, in the sense of Mark Wieder (and TMHO).
___
use-livecode mailing list
use-livecode@list
Couldn't you just get the globalLoc of the field and set the stack to that, or
an offset of it?
On January 9, 2016 6:37:52 PM CST, "Dr. Hawkins" wrote:
>
>
>Anyway, in this case, I'm popping up a stack over a field with the list
>of valid choices (I needed more than the built in popups). I jus
> On 10 Jan 2016, at 10:55 am, Dr. Hawkins wrote:
>
> As I look through screenLoc, screenRect(s), etc., I'm not seeing *any* way
> to figure out which screen an object is on, short of manually comparing
> elements of its rect to the various bits of screensRects.
put the screen of this stack int
I believe the screenRects is the only function that determines if you have
multiple monitors available. So comparing stack rects or plugging points
from your group rect/s into the globalLoc function would be the way to go.
The screenRect by itself determines the rect of the main monitor.
Regards
On Sat, Jan 9, 2016 at 4:26 PM, Mark Wieder wrote:
> I would think that ideally the user should be in control of whether
> something goes on one screen or another, and that this ability shouldn't be
> taken away from them.
>
AFAIK,live code offers no such option when opening a stack . . . there
On 01/09/2016 03:55 PM, Dr. Hawkins wrote:
As I look through screenLoc, screenRect(s), etc., I'm not seeing *any* way
to figure out which screen an object is on, short of manually comparing
elements of its rect to the various bits of screensRects.
In particular, I want to know if another stack
As I look through screenLoc, screenRect(s), etc., I'm not seeing *any* way
to figure out which screen an object is on, short of manually comparing
elements of its rect to the various bits of screensRects.
In particular, I want to know if another stack (or group) that I set the
position of will ac
11 matches
Mail list logo
