Re: Script locals in library stack script

2017-02-23 Thread J. Landman Gay via use-livecode
On 2/10/17 2:22 PM, J. Landman Gay via use-livecode wrote: I have set the LC preference to preserve variables. In the past I have rarely seen a script local lose its value, and never if there has been no script compile. I don't know exactly when it started but I was in 8.1.3 rc 1 when I noticed

Re: Script locals in library stack script

2017-02-13 Thread Bob Sneidar via use-livecode
I mised that this was on a web server. I should pay more attention. Bob S > On Feb 10, 2017, at 20:03 , J. Landman Gay via use-livecode > wrote: > > I know, that's why I didn't report it. I scoured the script looking for a > difference but I couldn't find

Re: Script locals in library stack script

2017-02-10 Thread J. Landman Gay via use-livecode
I know, that's why I didn't report it. I scoured the script looking for a difference but I couldn't find anything, the two queries were executed by the same handler. I looked for anything that would empty the variable and that wasn't there either. My current theory is creeping stack

Re: Script locals in library stack script

2017-02-10 Thread Bob Sneidar via use-livecode
I don't mean to oversimplify, but when customers call complaing that only one of several scan to SMB registrations is failing, I have to get them to see that if all the others are not failing ever, it cannot be a problem with the copier. If only one script local is getting reset, then it

Re: Script locals in library stack script

2017-02-10 Thread Bob Hall via use-livecode
—>There used to be a way to do that but I can't remember how, or else I forgot it on purpose because it didn't work. I think this is how you would do that… in IDE, debug menu->Add variable watch select the library stack and sVarA in the pop up. What I haven’t tested is the Condition. Maybe

Re: Script locals in library stack script

2017-02-10 Thread J. Landman Gay via use-livecode
On 2/10/17 5:56 AM, Bob Hall via use-livecode wrote: I’ve been wondering this myself. I’m going to try to create a recipe but it looks like the TTL of script local variables is different than what I thought I knew it to be. I “think” I started see this behavior about 8.1.0-ish timeframe but not

Re: Script locals in library stack script

2017-02-10 Thread Richard Gaskin via use-livecode
Bob Hall wrote: > So I guess I need to understand what is the TTL definition of a > script local variable? In the engine, script-local variables will retain their values throughout the session. If a script is edited, however, by default the recompilation of the script causes the

Re: Script locals in library stack script

2017-02-10 Thread Mike Kerner via use-livecode
This might explain the bizarre bug I'm experiencing with one of Monte's externals. I manage the calls to the various routines for the external from a library stack. Periodically, I end up somewhere in the code that I shouldn't be able to get to because of the values of various variables, and the

Re: Script locals in library stack script

2017-02-10 Thread Bob Hall via use-livecode
I’ve been wondering this myself. I’m going to try to create a recipe but it looks like the TTL of script local variables is different than what I thought I knew it to be. I “think” I started see this behavior about 8.1.0-ish timeframe but not sure. In the past few months I started to put

Re: Script locals in library stack script

2017-02-08 Thread J. Landman Gay via use-livecode
On 2/8/17 4:52 PM, Monte Goulding via use-livecode wrote: On 9 Feb 2017, at 9:32 am, J. Landman Gay via use-livecode wrote: I have a splash stack that opens a data stack from a server. The data stack has a substack which is used as a library with "start using".

Re: Script locals in library stack script

2017-02-08 Thread Monte Goulding via use-livecode
> On 9 Feb 2017, at 9:32 am, J. Landman Gay via use-livecode > wrote: > > I have a splash stack that opens a data stack from a server. The data stack > has a substack which is used as a library with "start using". > > The handlers in the library work okay. Some