Y coordinate for a line of text

[scott--- via use-livecode]

I’m needing to know the coordinate (Y is the tricky one) for a line of text. 
I’m not do a very good job at calculating it. I think I remember a newish LC 
command or function that achieved this but I can’t locate it in the dictionary. 
Am I imagining?

--
Scott Morrow

Elementary Software
(Now with 20% less chalk dust!)
web   https://elementarysoftware.com/
email sc...@elementarysoftware.com
booth1-800-615-0867

--








___
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

Re: Managing maximized windows on MacOS

[Paul McClernan via use-livecode]

I ran into this myself recently. LiveCode sends a resizeStack message when
you click the maximize "zoom box" button which you can intercept, but
there's no way to verify that it was the fullscreen zoom button that
generated the message. It would be nice if LC had the opposite of it's
iconifyStack
/ uniconifyStack messages for maximize, maybe "fullscreenify" or something
like that. It would also be nice if it played nice with LiveCode's
non-native fullScreen modes, as it is now the stack automatically gets
resized to the current screen's sized putting all the contents to the upper
left (0,0) origin point.
I have played around a bit with a separate LiveCode builder implementation
macOS native fullscreen that seems to behave a bit differently, if you lock
the resizable attributes it centers your stack on the screen without the
resizing. It's part of this LCB library here:
https://github.com/PaulMcClernan/LiveCode-LCB-macOSTools

On Mon, Nov 4, 2019 at 1:59 PM Giovanni via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi guys,
> from MacOS Mojave and on when you maximize a window (clicking on “+”
> button on windows main bar) the system maximize the window on the entire
> screen hiding all the system bars and moving the window on a different
> “virtual” space.
>
> Is there a way using LC to manage this window status?
> It’s possible to detect the window maximization (I.E. in a message) and
> manage the actions to activate when the window goes to this status or go
> back to the normal status?
>
> Thank you in advance for your tips!
>
> Regards
> ___
> 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
>
___
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

[ANN] This Week in LiveCode 201

[panagiotis merakos via use-livecode]

Hi all,

Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!

Read issue #201 here: http://bit.ly/2CzA0oR

This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around the open source project. New issues will be
released weekly on Mondays. We have a dedicated mailing list that will
deliver each issue directly to you e-mail, so you don't miss any!

If you have anything you'd like mentioned (a project, a discussion
somewhere, an upcoming event) then please get in touch.


-- 
Panagiotis Merakos 
LiveCode Software Developer

Everyone Can Create Apps 
___
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

Re: Atom Linting

[Brian Milby via use-livecode]

I have it working on Mac and Linux.  I’m not seeing it work properly on Win10 
though.  I did ensure all plugins were updated and Atom was at the latest 
version.

Thanks,
Brian
On Nov 11, 2019, 1:53 PM -0500, Ralf Bitter via use-livecode 
, wrote:
>
> > On 10. Nov 2019, at 03:12, Brian Milby via use-livecode 
> >  wrote:
> >
> > When I tried, I had to make an additional change
> > to get things to work.
>
>
> Brian, does linting LC code work for you an Mac OS too?
> On Ubuntu it works here as expected but since recently on Mac OS I get:
>
> [Linter] Error running language-livecode
>
> and the console reads:
>
> TypeError: Cannot read property 'setEncoding' of undefined
>
>
> Ralf
> ___
> 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
___
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

Re: Amazing how forgiving the older LC engines are...

[Tom Glod via use-livecode]

Yup.While upgrading from 7 to 8 and from 8 to 9 I had several "I can't
believe this code worked" moments.  I prefer an unforgiving interpreter.

thats why I fell in love with Rust and its ridiculously unforgiving
compiler.  Haven't had to use it yet, but look forward to it.

On Mon, Nov 11, 2019 at 9:01 AM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I just got bit by how forgiving older LC engines version are.
>
> Migrating a stack from LC6.7.11 to LC9.5.1. There is a handle to perform
> a "select all" on a particular list field where "select all" means
> select all lines but the first. The code was essentially:
>
>put empty into tLineList
>repeat with i=2 to the number of lines in fld 1
>  put i & cr after tLineList
>end repeat
>delete last char of tLineList
>set the hilitedLines of fld 1 to tLineList'
>
> This throws an script execution error under LC9.0.5 or 9.5.1 when trying
> to execute  the last line, but works perfectly well under LC6.7.11 and
> earlier.
>
> The problem, of course, is that the hilitedLines is supposed to be a
> COMMA delimited list, not a CR delimited list. Even the LC6.7.11
> Dictionary states comma delimited. And yet, LC6.7.11 and earlier happily
> allowed and handled correctly wither comma or cr delimited lists for the
> hilitedLines property.
>
> Simple change of Cr to comma fixes the routine for LC9xx
>
> I am not sure in what more recent LC versions this list flexibility went
> away (7? 8? 9?) but I have mixed feelings that it did go away. On one
> hand, I think the versatility of the older engine in forgiving and
> working with bad syntax was amazing. On the other had, had they been
> stricter, I would have discovered this bug long ago.
>
>
>
>
>
> ___
> 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
>


-- 
Tom Glod
Founder & Developer
MakeShyft R.D.A (www.makeshyft.com)
Office:226-706-9339
Mobile:226-706-9793
___
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

Re: Atom Linting

[Ralf Bitter via use-livecode]

> On 10. Nov 2019, at 03:12, Brian Milby via use-livecode 
>  wrote:
> 
>   When I tried, I had to make an additional change
> to get things to work.  


Brian, does linting LC code work for you an Mac OS too?
On Ubuntu it works here as expected but since recently on Mac OS I get:

[Linter] Error running language-livecode

and the console reads:

TypeError: Cannot read property 'setEncoding' of undefined


Ralf
___
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

Amazing how forgiving the older LC engines are...

[Paul Dupuis via use-livecode]

I just got bit by how forgiving older LC engines version are.

Migrating a stack from LC6.7.11 to LC9.5.1. There is a handle to perform 
a "select all" on a particular list field where "select all" means 
select all lines but the first. The code was essentially:


  put empty into tLineList
  repeat with i=2 to the number of lines in fld 1
    put i & cr after tLineList
  end repeat
  delete last char of tLineList
  set the hilitedLines of fld 1 to tLineList'

This throws an script execution error under LC9.0.5 or 9.5.1 when trying 
to execute  the last line, but works perfectly well under LC6.7.11 and 
earlier.


The problem, of course, is that the hilitedLines is supposed to be a 
COMMA delimited list, not a CR delimited list. Even the LC6.7.11 
Dictionary states comma delimited. And yet, LC6.7.11 and earlier happily 
allowed and handled correctly wither comma or cr delimited lists for the 
hilitedLines property.


Simple change of Cr to comma fixes the routine for LC9xx

I am not sure in what more recent LC versions this list flexibility went 
away (7? 8? 9?) but I have mixed feelings that it did go away. On one 
hand, I think the versatility of the older engine in forgiving and 
working with bad syntax was amazing. On the other had, had they been 
stricter, I would have discovered this bug long ago.






___
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