Re: Please add a way to Name my own Controls
Posted: Fri Sep 16, 2011 6:30 am
Code: Select all
topLevel stack "revApplicationOverview"LiveCode Forums.
Questions and answers about the LiveCode platform.
https://forums.livecode.com/
Please add a way to Name my own Controls
Page 3 of 3
Re: Please add a way to Name my own Controls
Posted: Fri Sep 16, 2011 7:23 am
Re: Please add a way to Name my own Controls
Posted: Fri Sep 16, 2011 7:43 am
Thanks. I didn't think of palette.
I'm making grr sounds now too. Know anyway to unfreeze LC when it's not in a loop, or capture a stack from memory? I just finished a protocol parser in one long sitting and was so focused I forgot to save as I went. Vote for the auto save feature request
I'm making grr sounds now too. Know anyway to unfreeze LC when it's not in a loop, or capture a stack from memory? I just finished a protocol parser in one long sitting and was so focused I forgot to save as I went. Vote for the auto save feature request
Re: Please add a way to Name my own Controls
Posted: Fri Sep 16, 2011 7:59 am
UnFreeze LC when its not in a loop.
Script editor has stopped - press the stop button
A scripting error message has poped up somewhere behind other windows
-- msgbox: set the raisewindows to true
See if you can open the app browser
and find the object that has the script in it and see if you can right click - edit script
you may have to: toplevel this stack
thats my limited knowledge
Script editor has stopped - press the stop button
A scripting error message has poped up somewhere behind other windows
-- msgbox: set the raisewindows to true
See if you can open the app browser
and find the object that has the script in it and see if you can right click - edit script
you may have to: toplevel this stack
thats my limited knowledge
Re: Please add a way to Name my own Controls
Posted: Fri Sep 16, 2011 9:33 am
No, it was locked solid, with an unresponsive empty Answer dialog box. I went into the LC process in memory and started suspending threads (they were all hung on "Waiting for user input" on the empty dialog box) but that was a long shot. At least it was easier to write the same code the second time around