LiveCode Forums.

..........

What fun! This code really makes me smile, up to now I have being creating invisible label fields to leave myself instructions this is so much better. One minor point is I had to wrap the code in a try catch statement as I have some commercial plugins running which use password protected stacks and the script throws an error it it is unable to access these stacks.

Do this "put" statements cause any problems when the code is compiled and there is no message box to receive them (I know there is a switch but...)?

best wishes

Simon

Hermann I LIKE that script!

..........

Hermann better to wait for one of the other 'big cheeses' from the LiveCode universe (and you, by the way are a big cheese) as I only class myself as a little cheese and pineapple combination on a cocktail stick

Regarding 'put' statements in standalones, I'm the same as you in that I've never yet password protected a stack, but during development I have run compiled standalones with 'put' statements in them that in the IDE would go to the message box - and have never noticed a problem (although I comment them out before releasing software)

PS: please forgive my use of the 'c' word

..........

A big cheese is usually round and portly, and aged. I am mainly the third.

I think that all one needs to be one is to have paid ones dues. If you once programmed on a Mac Plus, you are a great round.

Craig

Paul apologies for encouraging further 'drift' in your thread

Hermann well I think you have displayed your credentials in your last posting (I had no idea about exploding Corsican cheese and had to look it up) - in fact I suspect you would out-class me in every type of dairy product

..........

Do this "put" statements cause any problems when the code is compiled and there is no message box to receive them

In standalones, CGIs, or any other situation where the message box is unavailable, all put statements that don't have a destination defined go to stdout. Until Apple changed things in Mavericks, you could read the output in Console, which was a very handy debugging technique. I've put in a bug report to restore the behavior. Whatever method can read stdout in other OSs should work in those too.