I assume ALL the terms for LCB are included there.
The problem (as ever with the Dictionary) is knowing the term I want to look up . . .
What terms to look up.
-
richmond62
- Livecode Opensource Backer
- Posts: 10415
- Joined: Fri Feb 19, 2010 10:17 am
What terms to look up.
-
I assume ALL the terms for LCB are included there.
The problem (as ever with the Dictionary) is knowing the term I want to look up . . .
I assume ALL the terms for LCB are included there.
The problem (as ever with the Dictionary) is knowing the term I want to look up . . .
Re: What terms to look up.
Richmond, I am afraid that the sample dictionary entry you chose is case of documentation error:richmond62 wrote: Mon Jul 15, 2024 2:26 pm The problem (as ever with the Dictionary) is knowing the term I want to look up . . .
The example for entry "AbsOperator" refers to "the trunc of"...
Kind regards
Bernd
-
richmond62
- Livecode Opensource Backer
- Posts: 10415
- Joined: Fri Feb 19, 2010 10:17 am
Re: What terms to look up.
Quite possibly.
Although that does not help me with my conundrum.
Although that does not help me with my conundrum.
Re: What terms to look up.
Which is?
Re: What terms to look up.
Richmond.
That is a problem with dictionaries in general. If you want to know how to spell "phlegm", you are going to have to already know something about the English language and then do some work.
Now you want to find a native LC element given only, say, a desire to find a command that solves some functionality you wish to implement. Same thing only worse; you are a "layer" below the example above.
I always recommend getting as close as you can, and then look at all the related terms. Those are invaluable, and help bridge the gap between the two "layers" of separation in the above.
Craig
That is a problem with dictionaries in general. If you want to know how to spell "phlegm", you are going to have to already know something about the English language and then do some work.
Now you want to find a native LC element given only, say, a desire to find a command that solves some functionality you wish to implement. Same thing only worse; you are a "layer" below the example above.
I always recommend getting as close as you can, and then look at all the related terms. Those are invaluable, and help bridge the gap between the two "layers" of separation in the above.
Craig