More weirdness

This is not a new one, but my latest problem has to do with code that doesn't appear to get executed unless there is a breakpoint in the code. In the past, this happened in preOpenxxx handlers and the consensus was that it was a timing issue of some sort. Now I'm getting it in a mouseUp button scr

Re: More weirdness

Pete- Thursday, September 27, 2012, 6:18:38 PM, you wrote: > This is not a new one, but my latest problem has to do with code that > doesn't appear to get executed unless there is a breakpoint in the code. Without some actual code to look at it's hard to make a relevant comment. However, lack o

Re: More weirdness

Next time this happens, go into the script in the editor, put a space in or type ANYTHING to set the dirty bit (as mentioned you cna delete it afterwards) hit the apply button and then save the stack and see if it works. This is another one that.. well i can't recall how it actually occurs, but t

Re: More weirdness

On 9/27/12 8:18 PM, Peter Haworth wrote: When I run the stack toplevel, all works fine. When I run the stack as a plugin without the breakpoint, the scrolling list field is not populated, no runtime error, no indication of any error of any sort. With the breakpoint, everything works perfectly.

Re: More weirdness

Thanks for the suggestions. I painstakingly went through my code starting at the last line and working back from there, setting a red dot breakpoint on each line, then seeing if that point was reached. I finally discovered that the last line of code that is executed successfully is "go stack tSta

Re: More weirdness

Peter Haworth writes: > I finally discovered that the last line of code that > is executed successfully is "go stack tStack", where tStack contains a > valid file path as returned in the it variable after the user selects a > file from a dialog. Something in the (pre)openstack/card chain is caus

Re: More weirdness

Thank you Mark, that fixed the problem. However, I'm not sure I can use that solution. Won't lock messages apply to the stack I'm opening as well as the stack which issues it? If so, that could interfere with the opened stack's processing. If nothing else though, it narrows down the problem to t

Re: More weirdness

Peter- Saturday, September 29, 2012, 11:36:34 AM, you wrote: > However, I'm not sure I can use that solution. Won't lock messages apply to > the stack I'm opening as well as the stack which issues it? If so, that > could interfere with the opened stack's processing. Well, yes, that's the whole

Re: More weirdness

This is lcStackBrowser, it has to open stacks and allow them to do whatever they do. This happens with any stack that I open, it's not just one particular stack. I even created a new main stack with no objects, no scripts of any sort, then opened it and got the same problem. And here&#

Re: More weirdness

That prompted me to see what happened if I removed the answer file dialog and just hardcoded a stackfile path. Guess what - everything works perfectly. So something about the answer file dialog is causing this problem to occur. The command is: * * *answer* file "Select stackfile to open" with *t

Re: More weirdness

On 9/29/12 9:15 PM, Peter Haworth wrote: That prompted me to see what happened if I removed the answer file dialog and just hardcoded a stackfile path. Guess what - everything works perfectly. So something about the answer file dialog is causing this problem to occur. The command is: * * *ans

Re: More weirdness

Pete- Saturday, September 29, 2012, 7:01:03 PM, you wrote: > This is lcStackBrowser, it has to open stacks and allow them to do whatever > they do. This happens with any stack that I open, it's not just > one particular stack. I even created a new main stack with no objects, no > scripts of any

Re: More weirdness

Hi Jacque, Thanks for the suggestion. Initially, I thought this was occurring in the plugin version of the stack (which runs modeless), but I can reproduce it now in a regular toplevel stack. Pete lcSQL Software On Sat, Sep 29, 2012 at 7:29 PM, J. Landman Gay wrote: > Ma

Re: More weirdness

HI Mark, I suspected front script problems too. The only message my front script traps regarding the opening of stacks is openStack; all my front script handlers have an initial check to ignore messages that originate from an IDE stack by looking for stack names beginning with "rev" or, as you poin