Empty fields and controls after testing

Joe Lewis Wilkins pepetoo at cox.net
Tue Oct 25 19:49:31 CDT 2011


Mike,

I think your approach to creating something in LC is faulty. The vast majority of the time you're going to want any coding you've done within controls to "stick" as you say. You mention Edit Mode. I never even leave testing mode. I suppose you "may" want to do that from time to time; but, basically, you create "controls" and write handlers in them (stacks and cards and buttons and fields) and test them immediately. That was the HC way of doing things and I still do that with LC. Or am I the one who is out in left field?

Joe Wilkins
Architect

On Oct 25, 2011, at 5:39 PM, Admin wrote:

> 
> 
> One thing that truly bugs the hell out of me with Live Code is that
> when I am done designing/programming and want to test it, the data is
> now a part of the program. 
> 
> What I mean is, say you have and edit box
> and you go to test the program and type stuff in the edit box then go
> back to edit mode, the text is still there. Same
> 
> goes for captions and
> other stuff - any changes made in test mode sticks. 
> 
> Is there a way to
> test a program and when you go back to edit mode, it initializes
> everything so that all controls are blank. 
> 
> As it stands now, I have to
> write a custom button that when pressed, wipes all fields/controls and
> puts them back to their empty original state. It's a pain in the
> ass.
> 
> No other language I program in does this.
> 
> Any thoughts?
> 
> Mike
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



More information about the use-livecode mailing list