Re: Problem resizing a stack

Bob, You're missing the point. Everything works exactly as coded when the stack is not run as a plugin. The problems I've described only occur when the stack is run as a plugin. It's mtto anyway becasue I'm not executing that code anywhere now since I that property only needs to be set once. Pet

Re: Problem resizing a stack

Belay my last just noticed you were talking about preOpenCard. I think my eyes are dyslexic. > Why do it there? Can you put it in the opencard handler of the script of the > first card? I have found that some things don't work as expected in > preOpenstack. I would imagine changing the propert

Re: Problem resizing a stack

Why do it there? Can you put it in the opencard handler of the script of the first card? I have found that some things don't work as expected in preOpenstack. I would imagine changing the properties of an open stack would cause problems, since the stack is not technically "open" yet. If you try

Re: Problem resizing a stack

Thanbks Mark. SOunds like Powedebug would be a great hep - where can I get it? But I'm still puzzled why setting the liveresize of a stack would cause all these issues - that doesn;t seem to fit any of the situations where debug doesn't return errors. All I know is that without that statement, a

Re: Problem resizing a stack

Pete- Several things will turn breakpoints off and put the IDE's debugger back into run mode. Debugging through system stacks (any stack with a name starting with "rev", the message box, etc), stepping through send and dispatch commands, etc. There's some serious hackage in PowerDebug to handle t

Re: Problem resizing a stack

That explains a lot! So any of the library calls (like the database or libURL libraries) would result in this behavior? Pete lcSQL Software On Tue, Aug 28, 2012 at 7:58 PM, J. Landman Gay wrote: > On 8/28/12 8:56 PM, Dr. Hawkins wrote: > > Why the debugger finds breakpoi

Re: Problem resizing a stack

On 8/28/12 10:22 PM, Dr. Hawkins wrote: On Tue, Aug 28, 2012 at 7:58 PM, J. Landman Gay wrote: Breaks are ignored if the IDE is executing one of its own scripts. Any time it needs to take a tangent into one of its own libraries, breakpoints turn off. I understand that, and it makes sense. Bu

Re: Problem resizing a stack

On Tue, Aug 28, 2012 at 7:58 PM, J. Landman Gay wrote: > Breaks are ignored if the IDE is executing one of its own scripts. Any time > it needs to take a tangent into one of its own libraries, breakpoints turn > off. I understand that, and it makes sense. But when I have a breakpoint,, then mayb

Re: Problem resizing a stack

On 8/28/12 8:56 PM, Dr. Hawkins wrote: Why the debugger finds breakpoint to be a mere suggestion rather than an imperative is beyond me . . . Breaks are ignored if the IDE is executing one of its own scripts. Any time it needs to take a tangent into one of its own libraries, breakpoints tur

Re: Problem resizing a stack

Or in LA, where a red light means only 3 more cars get to go. .Jerry On Aug 28, 2012, at 7:47 PM, Peter Haworth wrote: > It's kinda like driving in Shanghai - red lights are just a suggestion. > Pete > lcSQL Software > > > > On Tue, Aug 28, 2012 at 6:56 PM, Dr. Hawkins

Re: Problem resizing a stack

It's kinda like driving in Shanghai - red lights are just a suggestion. Pete lcSQL Software On Tue, Aug 28, 2012 at 6:56 PM, Dr. Hawkins wrote: > Why the debugger finds breakpoint to be a mere suggestion rather than > an imperative is beyond me . . . > __

Re: Problem resizing a stack

On Tue, Aug 28, 2012 at 9:39 AM, Peter Haworth wrote: > I noticed that putting breakpoint commands in my preOpenCard script was not > having any effect, depending on where I put them. I frequently find it necessary in preOpenStack to answer "About to break" with ok breakpoint if there has been

Re: Problem resizing a stack

Thanks Mark and Bob. Unfortunatlet neither of those methods resulted in an error message. Oh well, I'm just happy that my stack works again, time to move on. Pete lcSQL Software On Tue, Aug 28, 2012 at 9:49 AM, Mark Wieder wrote: > Pete- > > Tuesday, August 28, 2012, 9

Re: Problem resizing a stack

I wonder if wrapping all the code in preOpenStack with a try catch would generate an error you could look at to get a clue as to why that bit of code was tossing an error. Bob On Aug 28, 2012, at 9:39 AM, Peter Haworth wrote: > But I can't help but wonder why that statement would cause a pro

Re: Problem resizing a stack

Pete- Tuesday, August 28, 2012, 9:39:42 AM, you wrote: > But I can't help but wonder why that statement would cause a problem in a > plugin but not in a regular stack, and perhaps even more worrying, why no > runtime error was reported. No runtime errors are reported in system stacks by default

Re: Problem resizing a stack

OK, I figured out what the problem is although I don't have a clue why it's a problem. I noticed that putting breakpoint commands in my preOpenCard script was not having any effect, depending on where I put them. I assumed that was happening because the code never reached the breakpoint for some

Re: Problem resizing a stack

Yes, there weren't any. Pete lcSQL Software On Tue, Aug 28, 2012 at 8:32 AM, Bob Sneidar wrote: > Pete, I believe that the solution post said something about some custom > properties that were left that were messing things up. Did you look at the > custom properties of t

Re: Problem resizing a stack

Pete, I believe that the solution post said something about some custom properties that were left that were messing things up. Did you look at the custom properties of the objects? Bob On Aug 27, 2012, at 6:45 PM, Peter Haworth wrote: > Thanks Bob, I read that and there is one common factor -

Re: Problem resizing a stack

Hi Jacque, The stacks opened modeless - I configure it that way by setting the crop cREVLoadInfo["mode"] to "modeless" when it is prepped for release. I'll have to check through the preOpenCard code to see if it uses "this stack" anywhere, or somewhere in the handler that is called from preOpenSta

Re: Problem resizing a stack

On 8/27/12 6:55 PM, Peter Haworth wrote: My stack resizes correctly if I send a message to the handler that does the resizing from the message box after the stack is displayed but the same handler does nothing when executed in preOpencard, even when the code is to send the message in zero millis

Re: Problem resizing a stack

> just put some code after openCard/openStack,etc types of handlers. I > hate > >>> that this might be so, but it seems to account, or at least forgive, > >>> certain timing and event queue issues that are inherent in those types > of > >>> messages. > &

Re: Problem resizing a stack

hate >>> that this might be so, but it seems to account, or at least forgive, >>> certain timing and event queue issues that are inherent in those types of >>> messages. >>> >>> >>> Try it. I don't think there is a formal methodology

Re: Problem resizing a stack

in those types of >> messages. >> >> >> Try it. I don't think there is a formal methodology for it all, it just >> seems to work. The fact that you can step through code, but not execute in >> real time, makes me think it could solve the problem. >> &

Re: Problem resizing a stack

ink there is a formal methodology for it all, it just > seems to work. The fact that you can step through code, but not execute in > real time, makes me think it could solve the problem. > > > Craig Newman > > > > -Original Message- > From: Peter Haworth &g

Re: Problem resizing a stack

Nice idea, I'll probably do something similar. The problme in my case was caused by the Geomerty Manager doing its thing when I resized the stack. The stack did actually resize but the gap between the bottom of the visible field and the bottom of the stack satyed the same because of GM so it look

Re: Problem resizing a stack

Hi from Beautiful Brittany, Peter, I have a simple mechanism in all of my stacks which allows me to show or hide a bottom line of debugging buttons. I have a tiny hidden button set in the same place in my stacks (usually at the top/left junction of a rectangle defining the work area of the stack.

Re: Problem resizing a stack

or it all, it just > seems to work. The fact that you can step through code, but not execute in > real time, makes me think it could solve the problem. > > > Craig Newman > > > > -Original Message- > From: Peter Haworth > To: How to use LiveCode > Sent: F

Re: Problem resizing a stack

> > > Craig Newman > > > > -Original Message- > From: Peter Haworth > To: How to use LiveCode > Sent: Fri, Aug 24, 2012 6:09 pm > Subject: Problem resizing a stack > > > A stack I'm working on has a group at the bottom that, at startup, needs to &

Re: Problem resizing a stack

ow to use LiveCode Sent: Fri, Aug 24, 2012 6:09 pm Subject: Problem resizing a stack A stack I'm working on has a group at the bottom that, at startup, needs to be hiddenor visible depending on preference setting. I want to adjust the bottom of the stack depdning on whether the group is hid

Problem resizing a stack

A stack I'm working on has a group at the bottom that, at startup, needs to be hiddenor visible depending on preference setting. I want to adjust the bottom of the stack depdning on whether the group is hidden or not. In a preOpenCard handler, if the preference requires the group to be hidden an