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 . . . )
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 a
.
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
Lin
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
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 al
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...@gm
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
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 a
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"
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 concatenat
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-"
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 "fil
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
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.
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.
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-
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 ima
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
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
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
Th
20 matches
Mail list logo
