Re: How to compile in earlier versions using new keywords?

The chained behavior solution needs any version specific code you want to be moved to a behavior for that version and uses the lack of script compilation as a feature. I prefer it to the string based solutions because the execution is faster. Cheers Monte Sent from my iPhone > On 10 Apr 2016

Re: Standalone (and stack in IDE) getting larger on each launch

setting the destroystack true or false had no effect. I tried to create a test stack to replicate the issue but couldn't which implies I guess that it is something in my stack doing it. For now I have moved the sizing handler further up the start chain and at least I have kept the increase constant

Re: How to compile in earlier versions using new keywords?

What I had in mind with that is a script part of the following form that should (but doesn't) compile in LC 6/7/8: if char 1 of the version > 6 then repeat for each trueword w in str ... end repeat else repeat for each word w in str ... end repeat end if How does your

Re: How to compile in earlier versions using new keywords?

One solution I have used for this is chained behaviors: on mouseUp put GetWord(fld “IN”,1) into fld “OUT” end mouseUp — parent behavior won’t compile in LC 6 function GetWord pText, pWord return trueword pWord of pText end GetWord — grandparent behavior function GetWord pText, pWord ret

POLL: LiveCode Server use

I have a poll in the forums to learn more about how people use LiveCode Server. Even if you don't use it, that's useful to know and there are options for that too. Please consider taking a moment to participate in the poll: The results m

Re: How to compile in earlier versions using new keywords?

For a while, LC 7 and 8 where linked in the sense, that, besides widget syntax, new keywords/functions/properties of LC Script were added to both. Actually they are already unlinked (in this sense), for example by the new "replace styled" function. This means we have the same problem as described i

Re: How to compile in earlier versions using new keywords?

On 04/09/2016 07:47 AM, -hh wrote: I have an idea, that may be more comfortable: If we could have a switch in LC 7+8 for parsing/compiling that temporarily disables one of the commenting methods, for example "//", we could use "version blocks" in new scripts: // usual comment line for all

Re: The TSA Android app

In a brighter note, now every CS Teacher have a new Real World Case to entice their students: "Look how easy you can earn your first million dollars..." :D Al -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/The-TSA-Android-app-tp4703144p4703276.html Sent from t

Re: How to compile in earlier versions using new keywords?

-hh wrote: @William > A nifty workaround. But this means, that we have to make two > script versions, and even three versions as soon as LC 8 is > "unlinked" (wrt compatibility) from previous versions. What does "unlinked" mean? As with most well-designed software, the new version is designed

Re: How to compile in earlier versions using new keywords?

@William A nifty workaround. But this means, that we have to make two script versions, and even three versions as soon as LC 8 is "unlinked" (wrt compatibility) from previous versions. @Craig I have some scripts where I use for example a switch for the itemdelimiter. if char 1 of the version <

Re: How to compile in earlier versions using new keywords?

This is one of the few cases where you have to use "do" . -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On April 9, 2016 8:45:18 AM -hh wrote: Is there a way to *compile* the following script in LC versions

Re: How to compile in earlier versions using new keywords?

Hernann. Maybe I do not understand. If a new native word is present in a certain version, it will not be recognized in an earlier one. There is no way to compile, it, any more than if you used any other extraneous word. Craig -Original Message- From: Earthednet-wp To: How to use L

Re: How to compile in earlier versions using new keywords?

Perhaps there is a way to have a text field that holds the appropriate script for the version, then you can set the script of btn xyz to fld "best script" on startup. Bill William Prothero http://es.earthednet.org > On Apr 9, 2016, at 6:11 AM, -hh wrote: > > Is there a way to *compile* the fo

How to compile in earlier versions using new keywords?

Is there a way to *compile* the following script in LC versions before 7? on mouseUp if char 1 of the version > 6 then put trueword 1 of fld "IN" into fld "OUT" else put word 1 of fld "IN" into fld "OUT" end mouseUp The use of the try structure doesn't help, the script doesn't even *comp