LiveCode Forums

That helps some. If those are your parameters then I'd do something like this: Place two input fields and two corresponding label fields on the card. Depending on the state of the pulldown menu, change the text of the label fields and/or hide label field 2 and text field 2. So this way you really on...

Peter- I have no idea what you're trying to do. You haven't given a lot of information, and some of it contradicts other parts. The example I posted (using ask statements) isn't at all how I would deal with things, but it does give you something to work with based on what you originally posted. From...

OK - how's the weather in Site Y? <g>

Not a lot of detail there, but it sounds like you've referenced external images instead of importing them into your stack.

Peter- try something like switch prop case 1 -- "CONDO" ask "what are the common charges?" if it is not empty then -- do something with it end if ask "what are the real estate taxes?" if it is not empty then -- do something with it end if break case 2 -- etc break case 3 break default end switch

Yeah - I just wish they were a bit more prominent on the web site. You really have to dig to find them.

In addition to Jan's advice, I'd also like to point out that in the dictionary you can open the Object menu on the left, then select Field and you'll have a handy listing of the properties and commands you can use with field objects. ...and be patient - coming from another high-level language progra...

...and I should point out that the glx2 script editor for OSX, Windows, linux, LiveCode and MetaCard is now open-source and is available for download at

https://bitbucket.org/mwieder/glx2/downloads

Do note that PowerDebug can debug standalones. Even so, I'd stay away from those "_internal" calls, even just in the IDE. If you're working strictly in the IDE then it's safe to call IDE functions that use them (calling colorscript itself should be ok) but the fact that the _internal calls are not e...

The warning in the docs is a good one to keep in mind, but I absolutely rely on the executionContexts because in most cases there's no other way to get that data for a stack trace. There are things in the IDE that would have to change somewhat radically if the executionContexts broke. The format has...

Once you get the hang of the existing language you won't feel any need for it I use dot syntax in my LiveCode scripts quite a bit. I realize this probably annoys people who are dogmatic about "no dot syntax", but I find it makes my code (IMO) more readable and helps keep my scripts organized. YMMV....

I don't think the split command is set up to handle multidimensional arrays. But here's a function that should do the job for you. on mouseUp pMouseBtnNo local tSQL local tDataArray -- initialize things to fake a return of SQL data put "1, 3.375, 360, 1" & cr & \ "2, 3.375, 360, 1" & cr & \ "3, 3.87...

Oooo - I second that - this would make a great presentation for livecode.tv

In the menubar's View menu, select LiveCode UI Elements in Lists. The revDebugger stack will then show up in the Application Browser.

Also, for a better debugging experience, check out PowerDebug.<g> On revOnLine or view the demo revlet at http://www.ahsoftware.net/PowerTools/Po ... DDemo.html

http://www.ahsoftware.net/PowerTools/BuyPowerDebug.irev