FWIW,
resizeStack and mousemove handlers have always been a 'difficult' to debug.
For this reason, I typically try and move my mouseMove handler to a mouseUp
while debugging. And turn off liveresizing for the stack to help debug
resizeStack.
___
use-live
I thought it was CTRL+BREAK
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
.runrev.com [mailto:use-livecode-
> boun...@lists.runrev.com] On Behalf Of Slava Paperno
> Sent: Sunday, June 26, 2011 3:33 PM
> To: 'How to use LiveCode'
> Subject: [[ SPAM ]] RE: one way to crash the IDE
>
> Thanks, Colin. Ctrl+period doesn't do that on Windows. Nor Ctrl+Q,
Thanks, Colin. Ctrl+period doesn't do that on Windows. Nor Ctrl+Q, Ctrl+C,
or Esc... maybe someone else can help us here. S.
> Don't know about Windows, but on Mac command-period breaks into the
> running script.
___
use-livecode mailing list
use-li
Don't know about Windows, but on Mac command-period breaks into the running
script.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.run
In case anyone is interested, here is one way to crash the 4.6.1 IDE in
Windows 7 so bad that you can't even switch to the running instance of Task
Manager: add to your resizeStack handler a reference to a non-existing
control, then in the Run mode try to resize the stack. Works every time.
Which
