THOUGHT: the [effective] [working] screenLoc

[Lagi Pittas]

" Windows taskbar can be resize to take up half the
primary screen by the user (we have NOT had any one do that - YET)"

Which reminds me of 3 variants of Murphy's law :-

Nothing can be made foolproof because fools are so ingenious.
Nothing is foolproof for a capable fool.

Lagi


On 4 June 2018 at 20:51, Paul Dupuis via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Okay, we're making progress:
>
> 2 people (Paul and Ralph) think having "the [effective] [working]
> screenLoc" might be a useful addition for the language for the likely
> effort to add it
> 2 people (Bob and Jacqueline) think that it is simple enough (which it
> is) to write your own function for this it is not worth the effort to
> add to the engine
>
> So far we have a tie.
>
> And, Jacqueline, screen resolutions can be changed dynamically on
> Windows (can't remember off the top of my head if the same is true for
> OSX). This changes the screenLoc. We also have customers who use
> multiple monitors, unplug them abruptly, change screen resolutions
> dynamically (say to connect to a projector) and so on, so are trying to
> make use of LC features like the desktopChanged message to recheck
> screen sizes and adjust windows in our app accordingly or re-position
> windows or recenter dialogs when a monitor is removed suddenly. Some
> user have "fat" taskbars (a lot of open stuff on them since the Windows
> toolbar can be resized)  and the center of the working screen area is
> decidedly not the center of the current resolution of the primary
> monitor. In fact, the Windows taskbar can be resize to take up half the
> primary screen by the user (we have NOT had any one do that - YET)
>
>
> On 6/4/2018 12:07 PM, Paul Dupuis via use-livecode wrote:
> > Yes, that is why I said (read below) that if others did not think there
> > should be an effective and/or working key word for the screenLoc
> > function, I would roll my own based on the screenRect function. I was
> > asking whether other think the screenLoc function should or should not
> > have these keywords.
> >
> >
> > On 6/4/2018 11:55 AM, Bob Sneidar via use-livecode wrote:
> >> Seems like you could subtract item 1 from item 3 and item 2 from item 4
> of the effective screenRect to get what you need.
> >>
> >> Bob S
> >>
> >>
> >>> On Jun 4, 2018, at 08:08 , Paul Dupuis via use-livecode <
> use-livecode at lists.runrev.com> wrote:
> >>>
> >>> I posted the question below and got no responses so I thought I would
> >>> try again.
> >>>
> >>> I noticed that screenLoc has no effective or working keywords
> associated
> >>> with it in LC9 or earlier. It seems to me that it should and that if it
> >>> has been done for the screenRect(s), it should be a small enhancement
> to
> >>> add them to the screenLoc
> >>>
> >>> Do others agree? If so I will submit and enhancement entry to the
> >>> quality center. if not, I'll drop this discussion thread and roll my
> own
> >>> function based on the screenRect function.
> >> _______________________________________________
> >> 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
> >>
> >
> > _______________________________________________
> > 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
> >
>
>
> _______________________________________________
> 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