These aren't really gripes as much as little issues I have due to my own limitations when using Livecode.
I find them funny, and I am curious if anyone else has similiar funny issues...
#1 - I cannot remember whether to use "with" or "for" in a repeat statement... I have a sticky note on my computer reminding me the proper usage. If I had to program a robot to disarm a bomb and it included repeat statements, we'd all be blown to dust by now.
#2 - Because of the English-like nature of Livecode, I have a tendency of adding punctuation where it doesn't belong. For example:
if this=that, then doSomethingElse!
#3 - Similarly, I sometimes start adding words that don't belong, or I start moving out of Livecode into a regular sentance
if there is a file tFile there then put this thing over there
#4 - Finally, when I get frustrated I start swearing in my scripts... and I find it really annoying that the Livecode engine doesn't respond... (no example provided, you get the idea)
Silly Livecode Problems
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 9802
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: Silly Livecode Problems
Both forms are supported. If the Dictionary entry discussing those isn't clear let us know and we can clean it up.lucapearce wrote: ↑Wed Jul 31, 2019 4:09 am#1 - I cannot remember whether to use "with" or "for" in a repeat statement...
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: Silly Livecode Problems
I understand what your saying, lucapearce, I had similar difficulties myself when I started with Lc (excluding punctuation).
What really annoyed me was that the debugger often seemed less than helpful when hitting a situation like you describe in #2. I modified your example and entered it in the code window since this was such a classic for me...
The debugger, though, gives this unhelpful warning...
Of course, I never went so far as to curse in the scripts, but you can rest assure I was certainly inventing words on the spot in my head
What really annoyed me was that the debugger often seemed less than helpful when hitting a situation like you describe in #2. I modified your example and entered it in the code window since this was such a classic for me...
Code: Select all
on mouseUp
if tmpThis=that, then doSomethingElse!
end mouseUp
What do you mean there is no "then" ?!stack "Untitled 1": compilation error at line 3 (if: missing 'then') near "doSomethingElse", char 21
Of course, I never went so far as to curse in the scripts, but you can rest assure I was certainly inventing words on the spot in my head