LiveCode Forums.

Pleased not to be odd one out on this occasion, thank you.

Holding my breath until next week; maybe.

This has worked normally for me for decades, and a forum search found no-one else with the same problem, so I have raised it here rather than in Bug Triage. Suggestions welcomed: This script: on mouseUp set the useSystemDate to true put the long date into field "f1" end mouseUp Gives me "Wednesday, ...

Craig, thank you for commenting although my purpose in presenting that code was to check my logic and feasibility, whether my interpretation met expectations, not to represent something that I or anyone would code, nor do I imagine other than that an enhancement in a future release is needed for Con...

Before I request the enhancement, I wanted to make sure we were not doing anything which broke existing LC. The following is an implementation using IF...THEN and some booleans. Its operation appears to me to be wholly consistent with current documentation, plus the new Continue. I have organised it...

Sorry, my day is being overwhelmed but I will do this within 24 hours, trusting that The Originator is more placid than some other -inators...

cheers
David

So far we have (in order) busted, nobreak, continue, done.

Although having contributed nobreak, I now favour continue. So, why has nobody raised an enhancement request? I semi-volunteered earlier so I will do it tomorrow if the originator does not get in first.

This may help to clarify my comments, again. It was back on page 2 that I noted the sole reference to NaN that I could find for LC was in release notes for 9.5.0 dp-1 (hereafter RN9.5). It was most likely those 9.5 comments which triggered Dar into submitting 22274 (Review), 22275 (Resolved Unsuitab...

Sound, and you are more practised in LC than I am. When I notice something like that I am only trying to give fuller information to newer readers who may happen upon our code fragments.

put 1e10000 = infinity --> true or put "n & "a" & "n" --> nan Easy to do. It depends with what you start. However, no-one has put their hand up for practical working examples or relevance. nan is not a reserved word in LiveCode, unlike infinity (not INF). However, as it states in LiveCode documenta...

Jacque, while you are keenly inserting breaks, note your last one is redundant, there being no further statements within the switch.

Look for 'on arrowkey' or just 'arrowkey', anywhere in any script

Also, check under General in Preferences. The checkbox for "arrowkeys navigate through cards" should be off.

edit: clarify first line

I spent some minutes after my earlier post checking something. NAN is not in the Dictionary. NAN is not in the User Guide. These make sense because NAN is not in LiveCode . So, why document something not in LiveCode language, regardless of whether it is used under the hood in the engine? Does your v...

That is interesting information about IEEE 754 treatment of NAN in maths processing (albeit not all unknown to me). My considerable lack of conviction has nothing to do with the description but with the implied assumption and ultimately with the supposed benefit. A straw poll: Would all of those who...

...but doesn't allow you to forget to add the 'break' (as your case example is missing) hee hee :wink: Yes it does. :) I left it out deliberately, saving typing, because it is superfluous at that point, there being no further conditions, nor a Default. I tested my code for each of the conditions (a...

...allows equivalence to sequential IFs in a more readable block... See, now that I just don't get. How is 'if / then' any more or less readable than switch/case/{break | noBreak}. I agree with all of the not-quoted, in that there is no immediate problem with implementation of desired logic. For th...