And I was in a round about way saying I didn't think it was necessary to do this through the engine, since there was no clear performance gain, and the code to work around it is one or two lines. I should have been clearer.
Bob S > On Jun 4, 2018, at 09:07 , Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com> 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@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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
