Re: 6.6 RC2 Release

[Richmond]

On 03/22/2014 06:30 AM, Dr. Hawkins wrote:

On Thu, Mar 20, 2014 at 9:13 PM, Bob Sneidar wrote:


I think that what you must mean by, "wrong" is, "presently inconvenient to
me",


Actually, I mean it as in, "driving on the left side of the road is wrong"
(unless you're in Britain, or . . . )




I drive a British car in Bulgaria [i.e. one that has the steering wheel 
on the 'wrong' side;
on the right], I also have a car with the steering when on the 'right 
side' (on the left).


As I also visit Britain at least once every year, and drive a car while 
I'm there, I find
that the best way to avoid confusion is always to drive down the middle 
of the road

except in places where there is a divided highway.

Richmond.

___
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: Request to makers of add-ons

[Richard Gaskin]

James Hale wrote:

> I really enjoy looking at software and appreciating the work
> the authors put in to their products.
> The same goes for all the helpful add-ons that are written for
> Livecode.
> I have quite a few and really appreciate their utility.
> But I have one request for authors of add-ons that require the
> installation of a library or "engine" in our projects.
> Please put a check in your demo/help/install stacks that check for
> the presence of the library BEFORE trying to load another copy.

That's an excellent idea.

This raises a question for an option that may be useful to add to the 
Standalone Builder:


Currently the SB allows us to specify external stacks, and at build time 
it'll copy those into a folder accompanying the app.


On OS X those files are copied into the bundle, but on Windows and Linux 
it puts them into a separate folder alongside the app.


If you're not using externals you wouldn't otherwise need that folder - 
why not - at least optionally - just copy the stacks into the stack file 
that becomes the standalone?


If the SB had an option for that we'd have a few benefits:

- Users of a given library wouldn't need multiple copies installed into 
their own mainstacks.  This not only solves your problem, but the 
additional problem of opening two different stacks which contain the 
same copied substack, along with simply saving space.


- One copy means one update to that stack file in the Plugins folder 
brings every subsequent build forward automatically.


- It obviates the need for an extra folder for the standalone, allowing 
you to deliver a single executable file if you like (provided you're not 
already using externals or other separate files).


H

The more I think about this, the more I realize this doesn't need to be 
in the SB at all, it could be a plugin that handles the savingStandalone 
message in a frontScript, examining a custom property in the mainstack 
(that it could provide a convenient UI to set) for a list of stack files 
to include, and then copy those in as needed.


Anyone have time to make such a tool?  If not I'll add it to my to-do list.



> There seems to be a bug in either the way Livecode handles this
> situation or how the add-on is responding to it.
> LC throws up a warning of an existing stack of that name (the
> library) but gets stuck in an endless loop trying to resolve it
> regardless of one's response to the warning ( be it purge, save or
> cancel.)
> I can only assume that LC does its thing but is then thrown back by
> the add-on trying to do its thing.

As much as I appreciate the simplicity of being able to address stacks 
by short name, stack name conflicts have been a problem for many of us 
from time to time, including yours truly.


I submitted an enhancement request to address this some time ago, but 
the current behavior is so ingrained in the engine that no clear way to 
resolve that has yet emerged:



At a minimum, the error handling for stack name conflicts in the IDE 
needs to be improved.  If you have a specific recipe for any such 
conflicts that are particularly troublesome, please file a bug report 
against it.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
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: Request to makers of add-ons

[Richmond]

.


This raises a question for an option that may be useful to add to the 
Standalone Builder:


Currently the SB allows us to specify external stacks, and at build 
time it'll copy those into a folder accompanying the app.


On OS X those files are copied into the bundle, but on Windows and 
Linux it puts them into a separate folder alongside the app.


If you're not using externals you wouldn't otherwise need that folder 
- why not - at least optionally - just copy the stacks into the stack 
file that becomes the standalone?






The separate folder alongside the app is a large PIB; especially if one 
delivers one's finished product in a ZIP
file: I have had several problems with people who have just extracted 
the app itself and then junked the
zip file including the folder with the necessary libraries, at which 
point their app doesn't work properly.


I am well aware that a Mac OS X "app" is nothing of the sort, but a 
folder containing the real app and all sorts

of ancillary stuff (and very clever it is too).

I wonder if there is not a way to "fold" all externals into Windows and 
Linux standalones so end-users are presented with

an apparently monolithic files as Mac users are.

Richmond.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[Dr. Hawkins]

On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:

> One of my two favorite beers... Any ice cold Belgian beer and Guiness.
>  Nothing else will do.
>

American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 22/03/14 17:51, Dr. Hawkins wrote:

On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:


One of my two favorite beers... Any ice cold Belgian beer and Guiness.
  Nothing else will do.


American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.




"Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.

"Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.

"Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.

"Samuel Adams" Dark: a stout brewed in Boston, Mass.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[Peter M. Brigham]

Our daughter brews a really fine chocolate porter. (No actual chocolate in the 
brew, it's just what it's called.) She and her husband brewed the beer for 
their wedding last year.

This is wandering far afield now. But at least I didn't mention "cheese."   :-)

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig

On Mar 22, 2014, at 11:56 AM, Richmond wrote:

> On 22/03/14 17:51, Dr. Hawkins wrote:
>> On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:
>> 
>>> One of my two favorite beers... Any ice cold Belgian beer and Guiness.
>>>  Nothing else will do.
>>> 
>> American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.
>> 
>> 
> 
> "Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.
> 
> "Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.
> 
> "Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.
> 
> "Samuel Adams" Dark: a stout brewed in Boston, Mass.

___
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: [OT][[TL/DR] 6.6 RC2 Release

[PystCat]

Cheese..?  A nice extra sharp cheddar.

> On Mar 22, 2014, at 12:16 PM, "Peter M. Brigham"  wrote:
> 
> Our daughter brews a really fine chocolate porter. (No actual chocolate in 
> the brew, it's just what it's called.) She and her husband brewed the beer 
> for their wedding last year.
> 
> This is wandering far afield now. But at least I didn't mention "cheese."   
> :-)
> 
> -- Peter
> 
> Peter M. Brigham
> pmb...@gmail.com
> http://home.comcast.net/~pmbrig
> 
>> On Mar 22, 2014, at 11:56 AM, Richmond wrote:
>> 
>>> On 22/03/14 17:51, Dr. Hawkins wrote:
 On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:
 
 One of my two favorite beers... Any ice cold Belgian beer and Guiness.
 Nothing else will do.
>>> American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.
>> 
>> "Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.
>> 
>> "Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.
>> 
>> "Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.
>> 
>> "Samuel Adams" Dark: a stout brewed in Boston, Mass.
> 
> ___
> 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: [OT][[TL/DR] 6.6 RC2 Release

[Richmond]

On 22/03/14 19:15, PystCat wrote:

Cheese..?  A nice extra sharp cheddar.


A good chunk of Stilton or French blue.




On Mar 22, 2014, at 12:16 PM, "Peter M. Brigham"  wrote:

Our daughter brews a really fine chocolate porter. (No actual chocolate in the 
brew, it's just what it's called.) She and her husband brewed the beer for 
their wedding last year.

This is wandering far afield now. But at least I didn't mention "cheese."   :-)

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig


On Mar 22, 2014, at 11:56 AM, Richmond wrote:


On 22/03/14 17:51, Dr. Hawkins wrote:

On Fri, Mar 21, 2014 at 7:49 PM, PystCat  wrote:

One of my two favorite beers... Any ice cold Belgian beer and Guiness.
Nothing else will do.

American Pale Ale, or IPA.  Most of what I brew is dry stout or pale ale.

"Kozel" (= goat), a fairly low alcohol dark beer from the Czech Republic.

"Stolichnaya", a heavy dark stout brewed in Stara Zagora, Bulgaria.

"Sweet Heart Stout", a fairly low alcohol sweet stout brewed in Scotland.

"Samuel Adams" Dark: a stout brewed in Boston, Mass.

___
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



___
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: 7.0 Issues

[BNig]

BNig wrote
> I noticed that plug-ins in 5.5 format save in 7.0 format when opened in
> 7.0 and the plug-in is saved. 
> This happens in spite of the the preference to save in legacy format. 

Upon further inspections this seems due to the fact that if one issues a
"save this stack" on "closeStack" it circumvents the preferences to save in
legacy format. 
That does affect e.g. plug-ins that save their state to themselves, as
lcStackBrowser does. And this will probably affect stacks that have their
"destroyStack" property set to true AND do a save on closeStack.

I don't know if this is a bug. But it surely makes the use of plug-ins that
save themselves a one way thing if one wants to test 7.0 DP1 alongside of
using older versions of Livecode.
A workaround would be to set the stackFileVersion to 5.5. in the affected
stacks, but that does not work for protected stacks.

Kind regards
Bernd




--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/7-0-Issues-tp4677380p4677419.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
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

multi-line constants? (for RSA keys)

[Dr. Hawkins]

RSA keys, as generated, are multiple lines, like
 "-BEGIN PUBLIC KEY-"
"ABC123"
"DEF456"
"-END PUBLIC KEY-"

I'm trying to do something like

constant mykey= "-BEGIN PUBLIC KEY-" \
& "ABC123"\
& "DEF456"\
& "-END PUBLIC KEY-"

but it appears that you can't concatenate strings like this . . . (using
6.6.0)

Is there a clean solution for this?

-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: multi-line constants? (for RSA keys)

[Richmond]

On 22/03/14 21:21, Dr. Hawkins wrote:

RSA keys, as generated, are multiple lines, like
  "-BEGIN PUBLIC KEY-"
"ABC123"
"DEF456"
"-END PUBLIC KEY-"

I'm trying to do something like

constant mykey= "-BEGIN PUBLIC KEY-" \
& "ABC123"\
& "DEF456"\
& "-END PUBLIC KEY-"

but it appears that you can't concatenate strings like this . . . (using
6.6.0)

Is there a clean solution for this?



Where are you getting your RSA key from?

If, for the sake of argument, you have it loaded into your stack as a 
string variable

 you could do something like this:

 put line 1 of RSA after myKey
   put line 2 of RSA after myKey
   put line 3 of RSA after myKey
   put line 4 of RSA after myKey

Richmond.

___
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: 7.0 Issues

[Peter Haworth]

Hi Bernd,
Which preference setting are you using?  The only one I could find is
titled "Preserve stack file format on stacks saved in legacy format" on the
Files and Memory tab.  No matter how I set that, if I save a stack in LC
from the File menu, I can't open it in versions prior to v7 ( get "file is
not a stack file" error).

This is with stacks with no closeStack handler.

Maybe I'm missing a preference setting somewhere?

Pete
lcSQL Software 
Home of lcStackBrowser  and
SQLiteAdmin 


On Sat, Mar 22, 2014 at 11:58 AM, BNig  wrote:

> BNig wrote
> > I noticed that plug-ins in 5.5 format save in 7.0 format when opened in
> > 7.0 and the plug-in is saved.
> > This happens in spite of the the preference to save in legacy format.
>
> Upon further inspections this seems due to the fact that if one issues a
> "save this stack" on "closeStack" it circumvents the preferences to save in
> legacy format.
> That does affect e.g. plug-ins that save their state to themselves, as
> lcStackBrowser does. And this will probably affect stacks that have their
> "destroyStack" property set to true AND do a save on closeStack.
>
> I don't know if this is a bug. But it surely makes the use of plug-ins that
> save themselves a one way thing if one wants to test 7.0 DP1 alongside of
> using older versions of Livecode.
> A workaround would be to set the stackFileVersion to 5.5. in the affected
> stacks, but that does not work for protected stacks.
>
> Kind regards
> Bernd
>
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/7-0-Issues-tp4677380p4677419.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> ___
> 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: 7.0 Issues

[BNig]

Peter Haworth wrote
> Hi Bernd,
> Which preference setting are you using?  The only one I could find is
> titled "Preserve stack file format on stacks saved in legacy format" on
> the
> Files and Memory tab.  No matter how I set that, if I save a stack in LC
> from the File menu, I can't open it in versions prior to v7 ( get "file is
> not a stack file" error).
> 
> This is with stacks with no closeStack handler.

That is the setting I meant. At first I also had the impression that it
would save to the new format regardless of the setting but then I switched
that off, closed preferences, reopend preferences, turned "Preserve stack
file format on stacks saved in legacy format" back on and quit Livecode 7.0. 
After that LC 7DP1 did follow the preference for saving from the menu or
command-s.

Kind regards
Bernd




--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/7-0-Issues-tp4677380p4677423.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
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: multi-line constants? (for RSA keys)

[Dr. Hawkins]

On Sat, Mar 22, 2014 at 12:37 PM, Richmond wrote:

> Where are you getting your RSA key from?
>
>
I'm generating it externally; it is to create the license keys for
purchasers.

I suppose putting it into a constant instead of a variable really doesn't
accomplish anything . . .


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 7.0 Issues

[Peter Haworth]

Confirmed.  Seems that the bug is that the Preference doesn't take effect
until next time you run Livecode.

I took a look at the Save As... dialog too.  It lists "Livecode Stack",
"Legacy Livecode stack (2.7)", and "Legacy Livecode Stack (2.4)" which are
the same settings as I see when running v6.x and v5.x. Shouldn't there be a
new one for v7?  If so, I'll enter a QCC report.

I also think the descriptions of the stack formats should echo the Livecode
versions they apply to, not some other cryptic number. How do I know what
versions of LC will work with 2.4 or 2.7?  I don;t recall when stack file
version 2.7 was introduced but if it was v5, it would be much clearer if
the Save As menu options read "Livecode stack (v", Livecode stack (v5-v7)", and Livecode stack (pre v5)", or
something similar.

Pete
lcSQL Software 
Home of lcStackBrowser  and
SQLiteAdmin 


On Sat, Mar 22, 2014 at 2:25 PM, BNig  wrote:

> Peter Haworth wrote
> > Hi Bernd,
> > Which preference setting are you using?  The only one I could find is
> > titled "Preserve stack file format on stacks saved in legacy format" on
> > the
> > Files and Memory tab.  No matter how I set that, if I save a stack in LC
> > from the File menu, I can't open it in versions prior to v7 ( get "file
> is
> > not a stack file" error).
> >
> > This is with stacks with no closeStack handler.
>
> That is the setting I meant. At first I also had the impression that it
> would save to the new format regardless of the setting but then I switched
> that off, closed preferences, reopend preferences, turned "Preserve stack
> file format on stacks saved in legacy format" back on and quit Livecode
> 7.0.
> After that LC 7DP1 did follow the preference for saving from the menu or
> command-s.
>
> Kind regards
> Bernd
>
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/7-0-Issues-tp4677380p4677423.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> ___
> 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: multi-line constants? (for RSA keys)

[Alex Tweedly]

On 22/03/2014 19:21, Dr. Hawkins wrote:

RSA keys, as generated, are multiple lines, like
  "-BEGIN PUBLIC KEY-"
"ABC123"
"DEF456"
"-END PUBLIC KEY-"

I'm trying to do something like

constant mykey= "-BEGIN PUBLIC KEY-" \
& "ABC123"\
& "DEF456"\
& "-END PUBLIC KEY-"

but it appears that you can't concatenate strings like this . . . (using
6.6.0)

Is there a clean solution for this?



constant doesn't allow any form of expression, you can't even do
constant mykey = "abc" & "def"

A "clean" solution ?
 - assign to a variable instead
 - custom prop
 - since you're generating it externally - put it in a fixed-name file, 
and have your script read that file in


btw if I take the above code, and convert from using a constant to a 
variable, I'd get

   put "-BEGIN PUBLIC KEY-" \
  & "ABC123"\
  & "DEF456"\
  & "-END PUBLIC KEY-" into myVar

but that means it's become a single line, instead of 4 lines.
Should it be
   put  "-BEGIN PUBLIC KEY-" &CR& \
  & "ABC123"  &CR& \
  & "DEF456" &CR& \
  & "-END PUBLIC KEY-" into myVar
??

-- Alex.



___
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

import snapshot

[John Dixon]

I have been using the following in LC 6.5.2 to take a snapshot of an area of a 
map, hiding the map and replacing it with the snapshot...

set the margins of the templateImage to 0
import snapshot from rect (0,40, the width of card "map", the height of card 
"map" -40 )
set the name of the last image of card "map" to "mapic"   

LC 6.6 does not like this at all !... it makes the snapshot about a quarter of 
the size in width but it seems to squash it a little in the vertical too...

I have tried the new snapshot syntax with at size, but can't get it to play...

Anyone found out how to take a snapshot in LC 6.6 yet ?
  
___
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: 7.0 Issues

[Mark Wieder]

Bernd-

Saturday, March 22, 2014, 11:58:33 AM, you wrote:

> That does affect e.g. plug-ins that save their state to themselves, as
> lcStackBrowser does.

This, by the way, is a very bad idea.
Stacks, especially plug-in stacks, should save their state variables
into a preferences file and not try to modify themselves. I learned
this lesson the hard way some time back and always ended up shooting
myself in many feet. Now I only have two.

-- 
-Mark Wieder
 ahsoftw...@gmail.com

This communication may be unlawfully collected and stored by the National 
Security Agency (NSA) in secret. The parties to this email do not 
consent to the retrieving or storing of this communication and any 
related metadata, as well as printing, copying, re-transmitting, 
disseminating, or otherwise using it. If you believe you have received 
this communication in error, please delete it immediately.


___
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: multi-line constants? (for RSA keys)

[Dr. Hawkins]

On Sat, Mar 22, 2014 at 5:35 PM, Alex Tweedly  wrote:

> constant doesn't allow any form of expression, you can't even do
> constant mykey = "abc" & "def"
>

*sigh*

I was hoping that  was doing something wrong.


>
> A "clean" solution ?
>  - assign to a variable instead
>

This is what I've been doing

>  - custom prop
>  - since you're generating it externally - put it in a fixed-name file,
> and have your script read that file in
>

But then it would be readable :)

>
> btw if I take the above code, and convert from using a constant to a
> variable, I'd get
>put "-BEGIN PUBLIC KEY-" \
>   & "ABC123"\
>   & "DEF456"\
>   & "-END PUBLIC KEY-" into myVar
>
> but that means it's become a single line, instead of 4 lines.
> Should it be
>put  "-BEGIN PUBLIC KEY-" &CR& \
>   & "ABC123"  &CR& \
>   & "DEF456" &CR& \
>   & "-END PUBLIC KEY-" into myVar
>

Yes, I blew that typing it in . . .



-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
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: 7.0 Issues

[J. Landman Gay]

On 3/22/14, 6:57 PM, Peter Haworth wrote:

I also think the descriptions of the stack formats should echo the Livecode
versions they apply to, not some other cryptic number. How do I know what
versions of LC will work with 2.4 or 2.7?  I don;t recall when stack file
version 2.7 was introduced


The numbers represent the version where the file format changed. File 
format 2.4 was introduced in Rev 2.4, format 2.7 was introduced in Rev 
2.7, etc. Each engine is backward compatible, so you can use any version 
of LC/Rev equal to or higher than the file format.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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