I just ran into this. If a variable contains “card foo” then the command open
card foo resolves to open card card foo. You can see the problem. There is no
card named card foo. Just foo.
Is this the problem you are seeing?
Bob S
On Nov 8, 2014, at 13:29 , Dr. Hawkins doch...@gmail.com
On Tue, Nov 11, 2014 at 1:55 PM, Bob Sneidar bobsnei...@iotecdigital.com
wrote:
I just ran into this. If a variable contains “card foo” then the command
open card foo resolves to open card card foo. You can see the problem.
There is no card named card foo. Just foo.
Is this the problem you
Editor field name changed? Thanks for that, need to update lcStackBrowser.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
On Fri, Nov 7, 2014 at 6:59 PM, J. Landman Gay
On Wed, Nov 5, 2014 at 6:55 PM, Peter Haworth p...@lcsql.com wrote:
I'd say that's a bug. It's good practice to use quotes around card and
stack names but unless there are any characters in those names like spaces,
etc, it shouldn't cause a problem without them.
The more I think about this,
On Fri, Nov 7, 2014 at 6:59 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
Not only did the name of the editor field change,
Hi Jacque,
Just looked into this as it would affect one of my products but I see the
same name for the editor field in 6.6 and 6.7 = Script. This is in group
Editor
Pete-
Saturday, November 8, 2014, 5:13:51 PM, you wrote:
Just looked into this as it would affect one of my products but I see the
same name for the editor field in 6.6 and 6.7 = Script. This is in group
Editor of card Main of stack revNewScriptEditor 1. Am I missing something?
Yeah, you
On 11/8/2014, 7:13 PM, Peter Haworth wrote:
On Fri, Nov 7, 2014 at 6:59 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
Not only did the name of the editor field change,
Hi Jacque,
Just looked into this as it would affect one of my products but I see the
same name for the editor field in
On Nov 6, 2014, at 4:58 PM, Peter Haworth wrote:
I spent an hour yesterday trying to track down a bug that turned out to be
caused by a misspelled variable name.
I don't use explicit variables, so I avoid misspelling variable names by using
Jaques' scriptPaint handler. Put this into a
Yeah, well, it all breaks in LiveCode 6.7. Which is a huge bummer because I've
relied on that handler for years and it's second nature now. Not only did the
name of the editor field change, which is easily fixed, but the control key,
among others, no longer triggers.
On November 7, 2014
I tried that. I just prefer declaring all variables and not have to bother
with extra key modifiers while typing.
I guess there'll never be a group agreement on the use of explicit
variables, i's just a matter of personal preference.
Pete
lcSQL Software http://www.lcsql.com
Home of
05, 2014 9:56 PM
To: How to use LiveCode
Subject: Re: 7.0.1-RC1 selectively not obeying open card in script?
I'd say that's a bug. It's good practice to use quotes around card and
stack names but unless there are any characters in those names like spaces,
etc, it shouldn't cause a problem without
, 2014 9:56 PM
To: How to use LiveCode
Subject: Re: 7.0.1-RC1 selectively not obeying open card in script?
I'd say that's a bug. It's good practice to use quotes around card and
stack names but unless there are any characters in those names like spaces,
etc, it shouldn't cause a problem
On Thu, Nov 6, 2014 at 12:06 PM, Ralph DiMola rdim...@evergreeninfo.net
wrote:
It is a bug but.another reason to use Strict Compilation Mode.
This is happening *in* that mode; it doesn't catch it.
The card stack combo are built from known names; apparently LC7 is
treating a word in the
On Thu, Nov 6, 2014 at 1:58 PM, Peter Haworth p...@lcsql.com wrote:
I had turned off Strict Compile Mode temporarily because of the name
shadows another variable bug which still hasn't been fixed and causes me
to quit and restart LC probably 6 times a day.
That was the primary reason I
I am suddenly seeing (with disastrous results) 7.0.1-RC1 ignore an open
invisible card foo of stack bar command. This in turn causes the
formattedHeight to quietly return 0.
I've stepped through the code, then set the vis to true, and seen it fail.
I've even added a line to open without the
Not likely as this has been working but check the result after the open
statement to see if some sort of error occurred.
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
On Wed, Nov 5,
On Wed, Nov 5, 2014 at 9:43 AM, Peter Haworth p...@lcsql.com wrote:
Not likely as this has been working but check the result after the open
statement to see if some sort of error occurred.
(ck is a simple routine to log/put messages. Here it is effectively a 1
argument put)
ck srcCd cr
On 11/5/2014, 12:35 PM, Dr. Hawkins wrote:
On Wed, Nov 5, 2014 at 9:43 AM, Peter Haworth p...@lcsql.com wrote:
Not likely as this has been working but check the result after the open
statement to see if some sort of error occurred.
(ck is a simple routine to log/put messages. Here it is
Maybe some sort of de-referencing problem? What happens if you:
go card scD_1207 of stack rawForms
Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
On Wed, Nov 5, 2014 at 10:35 AM, Dr.
On Wed, Nov 5, 2014 at 11:09 AM, Peter Haworth p...@lcsql.com wrote:
go card scD_1207 of stack rawForms
Apparently, it's the quotes. 5.5.4 could handle this without quotes; 7.0
cannot.
--
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
I'd say that's a bug. It's good practice to use quotes around card and
stack names but unless there are any characters in those names like spaces,
etc, it shouldn't cause a problem without them.
Maybe another side effect of Unicode in 7.0 Have you tried it in 6.6 or
6.7? If it works on those
21 matches
Mail list logo
