Re: Curious Dictionary Absense

Odd I searched for screen and drew a blank before but now it’s working even searching for screenr. Maybe I had an extra character like a space or something. Bob S > On Nov 6, 2024, at 11:20 AM, Craig Newman via use-livecode > wrote: > > The dictionary is good at finding fragme

Re: Curious Dictionary Absense

The dictionary is good at finding fragments of words, but not misspelled ones, So it will find lots of entries for “screen”, but only two for “screenR” and none for “screenRS” Craig > On Nov 6, 2024, at 1:05 PM, Bob Sneidar via use-livecode > wrote: > > Curiously, the screenRec

Re: Curious Dictionary Absense

The entry is “the screenrect”, no “S”. Craig > On Nov 6, 2024, at 1:05 PM, Bob Sneidar via use-livecode > wrote: > > Curiously, the screenRects is not in my dictionary. > > Bob S > > ___ > use-livecode mailing list >

Curious Dictionary Absense

Curiously, the screenRects is not in my dictionary. Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo

Re: Regular crash: Dictionary (API)

On 6/21/21 12:30 PM, David Bovill via use-livecode wrote: Anyone point me too an alternative Dictionary  - too many regular crashes using the built in one? TinyDictionary -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use

Re: Regular crash: Dictionary (API)

Anyone point me too an alternative Dictionary  - too many regular crashes using the built in one? 📆    Schedule a call with me On 11 Jun 2021, 19:46 +0100, David Bovill , wrote: > For several years I have a regular crash when opening the `Dictionary (API)` > - wondering the cause. Ever

Regular crash: Dictionary (API)

For several years I have a regular crash when opening the `Dictionary (API)` - wondering the cause. Everything else works as normal - latest MacOs and Livecode - spinning coloured ball and now dictionary stack displayed  - requires force quit. Doing that now. Third time today. 📆    Schedule a

Re: Problem with searching dictionary

looks like the search algo is not searching the body of the section just the title. Makes sense why, but there ought to be a checkbox somewhere to enable a deeper search. try searching for "tiny lc" dictionary somewhere, one one our users here made an alternative application for the

Problem with searching dictionary

to stop it searching deeper or is there a better way to search the dictionary? regards alex ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http:

Re: Dictionary

Ditto on the Dictionary! Cheers, Roger > On May 23, 2019, at 12:26 PM, R.H. via use-livecode > wrote: > > I agree that the dictionary often leaves guess work. > > The biggest problem I have with the dictionary is forgetting the name of a > function and trying to guess th

Re: Dictionary

After a year or more getting used to GIT, I am willing help. I know somewhere, buried in this list, is a tutorial on helping with the dictionary. Can a lesson be created on the subject? I keep asking a lot of ? and get great advice from the list, and save it. I might as well try a few edits

Dictionary

I agree that the dictionary often leaves guess work. The biggest problem I have with the dictionary is forgetting the name of a function and trying to guess the name. If there were lots of tags to look for... but... You must know at least the beginning of a name. And how can you even search not

Re: Us and them? [was Re: Livecode Dictionary]

If using a binary stack, ScriptTracker makes it easy to edit scripts in an external editor. Levure includes a server process that allows Sublime Text tell LC to reload a script only stack when saved from there (I don’t think it depends on the app itself being managed with Levure).  I use Atom be

Re: Us and them? [was Re: Livecode Dictionary]

On Thu, Jan 24, 2019 at 12:36 AM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > When I forked it I returned to a > editor separate from a debugger, each purpose-built for the task they do > YES. If I had a nickel for every time I expand the variable list while in the de

Re: Us and them? [was Re: Livecode Dictionary]

GLX2 was great at one time, but certain features added later, like code saving caused problems. I'd like to see GLX2 gone through and made stable again, and although Mark Weider has been very diligent to correct any issues that have sprung up in the past, no can expect him to continue brooding o

Re: Us and them? [was Re: Livecode Dictionary]

people and projects that might loom larger than the code. A UI-centered person might feel that it's in the wrong place and hate going into SE to make notes about UI. Although I do understand the passion to integrate something cool! Meanwhile dictionary comments could just go in the dic

Re: Us and them? [was Re: Livecode Dictionary]

Hi Curry - you wrote: A project wiki would fit in the SE better than it would the Dictionary, > of course, it would have more features and I could see that being a tab. > But then again user keyword comments would fit the Dictionary very well, > they could simply be added there. Having a

Re: Us and them? [was Re: Livecode Dictionary]

d either dive into the existing SE and fix it, or write my own. Life's too short not to have what we want. > The wiki sounds like a neat project. Simplicity helps, and whether to > locate it in the SE is a consideration. Besides performance, another > issue is that the original

Re: Us and them? [was Re: Livecode Dictionary]

city helps, and whether to locate it in the SE is a consideration. Besides performance, another issue is that the original proposal here was adding user comments back to the Dictionary. A project wiki would fit in the SE better than it would the Dictionary, of course, it would have more features an

Re: Us and them? [was Re: Livecode Dictionary]

+1 for Sublime. I do not code in it much, but there are plugins like for comparing two scripts to see differences. If I ever get around to converting my main app to Levure, I would probably use it more. Bob S > On Jan 23, 2019, at 10:52 , Trevor DeVore via use-livecode > wrote: > > On Wed,

Re: Us and them? [was Re: Livecode Dictionary]

Trevor DeVore wrote: > On Wed, Jan 23, 2019 at 12:39 PM Richard Gaskin wrote: >> >> And then there are the countless third-party text editors, some of >> which have LC-specific add-ons crafted by our community for them, >> like Trevor's plugin for Atom. I've been using Atom enough in web >> deve

Re: Us and them? [was Re: Livecode Dictionary]

On Wed, Jan 23, 2019 at 12:39 PM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > > And then there are the countless third-party text editors, some of which > have LC-specific add-ons crafted by our community for them, like > Trevor's plugin for Atom. I've been using Atom

Re: Us and them? [was Re: Livecode Dictionary]

Curry Kenworthy wrote: > What people need most in the Script Editor is to view and edit the > code itself smoothly, without jitters or delays Not hard to make one. A frontScript trapping the editScript message lets you do whatever you want. You can make a stack with a field and a Save button

Re: Us and them? [was Re: Livecode Dictionary]

e which camp I'm in, since I'm not fully "us" and not full "them", but a mish-mash of both and a lot of moving around in between those polarities. As long as each of us can use the workflows we prefer, does the distinction matter? > A typical casualty of this co

Re: Us and them? [was Re: Livecode Dictionary]

tor is already a bit chubby, huffing and puffing on many machines during a modest jog, and the Dictionary is waddling around even slower and shakier on my budget hardware than I move around myself as a handicap person. :D What people need most in the Script Editor is to view and edit the cod

Re: Us and them? [was Re: Livecode Dictionary]

h-mash of both and a lot of moving around > in between those polarities. > > As long as each of us can use the workflows we prefer, does the > distinction matter? > > > > > A typical casualty of this conflict is the cancelling of the ability > > of these ordinary

Re: Us and them? [was Re: Livecode Dictionary]

ile and was able to present it in the system browser on my Mac. The intended use is for a forked LiveCode repo which includes the dictionary. There you can use git to create a branch off of develop-9.0 and update dictionary entries. Once the edits are done, commit to your new branch and then on

Re: Us and them? [was Re: Livecode Dictionary]

lot of moving around in between those polarities. As long as each of us can use the workflows we prefer, does the distinction matter? > A typical casualty of this conflict is the cancelling of the ability > of these ordinary users to add notes to the dictionary, without > apparent thought

Re: Us and them? [was Re: Livecode Dictionary]

a bit chubby, huffing and puffing on many machines during a modest jog, and the Dictionary is waddling around even slower and shakier on my budget hardware than I move around myself as a handicap person. :D What people need most in the Script Editor is to view and edit the code itself smoot

Re: Us and them? [was Re: Livecode Dictionary]

vecode@lists.runrev.com> wrote: > > > > > > > > That license will not allow inclusion into the LiceCode dictionary as > it > > > requires any derivative works to carry the same license. For > integration > > > into the LiveCode project a CLA will

Re: Us and them? [was Re: Livecode Dictionary]

Tue, 22 Jan 2019 at 14:40, Brian Milby via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > > That license will not allow inclusion into the LiceCode dictionary as it > > requires any derivative works to carry the same license. For integration > > in

Re: Us and them? [was Re: Livecode Dictionary]

On Tue, 22 Jan 2019 at 14:40, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > > That license will not allow inclusion into the LiceCode dictionary as it > requires any derivative works to carry the same license. For integration > into the LiveCode proje

Re: Us and them? [was Re: Livecode Dictionary]

It sounds very ambitious. My main suggestion was for a shareable user additions part of the dictionary that could be incorporated into the main dictionary at some later date, if useful. It is so common to see user comments on web content, that I don’t see how there could be a problem with

Re: Us and them? [was Re: Livecode Dictionary]

Just to clarify, I didn’t really mean to suggest that there was a plan - it’s just that a lot of the creative energy around LC and its development seems to be going away from this as if it were bad, basically because it’s hard to do version control on binary stacks, as far as I can see. I do und

Re: Us and them? [was Re: Livecode Dictionary]

Two comments initially: That license will not allow inclusion into the LiceCode dictionary as it requires any derivative works to carry the same license.  For integration into the LiveCode project a CLA will need to be signed by each author and their contributions also submitted with copyright

Re: Us and them? [was Re: Livecode Dictionary]

I'm working on a solution for this - it's kind of ambitious and won't be ready to share publicly for about 3 months at a guess - but I'm happy to share it with anyone who want to use GitHub and get deep into the issue. *Quick outline of dictionary strategy* 1. It should b

Re: Us and them? [was Re: Livecode Dictionary]

ntime, that's a completely different matter.) > cancelling of the ability of these ordinary users to add notes > to the dictionary Yep, it's worthwhile to keep LC 6 handy for those notes! Highly valuable. Continuing user comments for LC 9+ would be a smart move. Richmond: > w

Re: Us and them? [was Re: Livecode Dictionary]

I agree with Richmond. There are many great suggestions for coding tricks, and workarounds that occur on this list. That wisdom remains in the archives, but is not necessarily obviously accessible to those of us who may be exploring an unfamiliar or poorly documented technique. The dictionary

Re: Us and them? [was Re: Livecode Dictionary]

ther people; so worrying about Microsoft, if one spends too much time on it can become fairly unhealthy: and what about Apple, Canonical, and so on and so forth? - My objection to bunging user stuff for the LiveCode dictionary on GitHub has nothing to do with Microsoft, but has a lot to do wit

Re: Us and them? [was Re: Livecode Dictionary]

Many developers do not trust Microsoft, and neither do I. Things may be fine right now, but it is the future that concerns me more. They can change their terms at anytime, and no one knows what they will do. Just a word of caution. Cheers, Rick > On Jan 20, 2019, at 2:50 PM, Richard Gaskin v

Re: Livecode Dictionary

On Sun, Jan 20, 2019 at 12:07 PM Tom Glod via use-livecode < use-livecode@lists.runrev.com> wrote: > > The permissions are over the top, but not intentional I am sure. > Agreed. I'm just waiting to see if: 1. My changes go in with the current state of affairs. 2. Someone from LC re-ups their cer

Re: Us and them? [was Re: Livecode Dictionary]

Rick Harrison wrote: > I do not believe most of LC’s users are interested in signing up > for GitHub and having to sign an agreement with new owner Microsoft > too. In what way has Girhub's TOS been changed after Microsoft's acquisition which would be a concern to LiveCode developers? -- Ric

Re: Livecode Dictionary

I think the LC team set things up so that its convenient for them in their workflow of growing & maintaining Livecode, ...its not so much our convenience per se. I think removing notes from the dictionary is a step backwards. This one needs correction. The permissions are over the top, but

Re: Livecode Dictionary

Rick Harrison wrote: > Now that Microsoft owns GitHub perhaps LC should consider > moving everything over to some other entity such as Bitbucket, > or SourceForge. > > What do you think? Personally, I think if it's good enough for the world's largest software project, the open source Linux kern

Re: Livecode Dictionary

On Sun, Jan 20, 2019 at 6:47 AM Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > LiveCode can’t use your contribution without the CLA. Someone from LC May > need to clarify the details. Since they release code as GPL and > Commercial, we need to assign copyright to them for

Re: Livecode Dictionary

On Sun, Jan 20, 2019 at 6:10 AM Trevor DeVore via use-livecode < use-livecode@lists.runrev.com> wrote: > > The newsletter also lists documentation bugs which need fixing. Here is a > link to the latest edition: > > > https://livecode.github.io/this-week-in-livecode/issue/2019/01/14/this-week-in-li

Re: Us and them? [was Re: Livecode Dictionary]

resources all over the internet doesn’t fit that model, yet that seems to be what we are dealing with now. Just my 2 cents for the day. Thanks for reading! Rick > On Jan 20, 2019, at 8:44 AM, Graham Samuel via use-livecode > wrote: > > Just covering this one point of Geoff’s in th

Re: Livecode Dictionary

Now that Microsoft owns GitHub perhaps LC should consider moving everything over to some other entity such as Bitbucket, or SourceForge. What do you think? Rick ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to su

Re: Livecode Dictionary

gt; > > I agree that the dictionary isn’t the easiest to update without a GutHib > > client, but dictionary updates can be done completely in a browser. > > > Yep, I figured that out after I spent several minutes looking for the > dictionary data and poking through the dictio

Re: Livecode Dictionary

On Sat, Jan 19, 2019 at 9:00 PM Geoff Canyon via use-livecode < use-livecode@lists.runrev.com> wrote: > 1. Not everyone (very few people?) understand how git/GitHub works. > 2. Even if you have a reasonable grasp of how to use git it's not obvious > how to contribute to the

Us and them? [was Re: Livecode Dictionary]

Just covering this one point of Geoff’s in the Dictionary discussion. I agree with his comment, and I think it’s symptomatic of a problem with the development of LC in the last few years: there is IMHO a conflict between the “everyone can code” philosophy that LC inherited (and greatly enriched

Re: Livecode Dictionary

On Sat, Jan 19, 2019 at 8:22 PM Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > I agree that the dictionary isn’t the easiest to update without a GutHib > client, but dictionary updates can be done completely in a browser. Yep, I figured that out after I s

Re: Livecode Dictionary

On Sat, Jan 19, 2019 at 8:11 PM Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > Interesting. I just checked on GitHub and the oauth token for LiveCode > was recently revoked automatically since it was not used. It’s been quite > a while since I did it and I can’t recall ab

Re: Livecode Dictionary

I agree that the dictionary isn’t the easiest to update without a GutHib client, but dictionary updates can be done completely in a browser.  The use of the browser widget for the display of the dictionary data is quite independent from the data itself.  Maybe the community could put a complete

Re: Livecode Dictionary

of how to use git it's not obvious > > how to contribute to the dictionary using git. I've maintained Navigator in > > git/GitHub for about a year, and I'm sure I don't know the detailed steps > > -- just the general sense of "clone the repository, make

Re: Livecode Dictionary

19, 2019 at 6:59 PM Geoff Canyon wrote: > 1. Not everyone (very few people?) understand how git/GitHub works. > 2. Even if you have a reasonable grasp of how to use git it's not obvious > how to contribute to the dictionary using git. I've maintained Navigator in > git/GitHub

Re: Livecode Dictionary

1. Not everyone (very few people?) understand how git/GitHub works. 2. Even if you have a reasonable grasp of how to use git it's not obvious how to contribute to the dictionary using git. I've maintained Navigator in git/GitHub for about a year, and I'm sure I don't kno

Re: Livecode Dictionary

Use Bernd's TinyDictionary. There everybody can add his own (private) notes. Download from "Sample Stacks" or http://livecodeshare.runrev.com/stack/825/TinyDictionary ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to s

Re: Livecode Dictionary

> On Jan 19, 2019, at 8:54 AM, Brian Milby via use-livecode > wrote: > > We have an even better option now. Contributions to the actual dictionary > can be submitted via GitHub. If you have to post this here, it means it needs to be more obvious in the Dictionary wrapper

Re: Livecode Dictionary

We have an even better option now.  Contributions to the actual dictionary can be submitted via GitHub. Thanks, Brian On Jan 19, 2019, 9:48 AM -0600, Richmond via use-livecode , wrote: > Some of those user entries were extremely useful. > > It would be good if user entries could be re

Re: Livecode Dictionary

Some of those user entries were extremely useful. It would be good if user entries could be restored to the dictionary once again. Richmond. On 19.01.19 9:49, Simon Knight via use-livecode wrote: Hi all, I have just read about two “issues” and both would be resolved or at least helped

Livecode Dictionary

Hi all, I have just read about two “issues” and both would be resolved or at least helped with a more detailed dictionary entry. Now in the dim distant past the RunRev dictionary use to allow humble users to add comments and examples which I for one found useful. Does anyone know why this

Re: how to refresh LC IDE dictionary after i changed a api.lcdoc file?

ode@lists.runrev.com> wrote: > Hi, > > i changed some information in an api.lcdoc file of an extension. In my > case i added some additional examples. Each new example with a leading > “Example:” tag. > How do i get that new information displayed in the dictionary. Even after > a resta

how to refresh LC IDE dictionary after i changed a api.lcdoc file?

Hi, i changed some information in an api.lcdoc file of an extension. In my case i added some additional examples. Each new example with a leading “Example:” tag. How do i get that new information displayed in the dictionary. Even after a restart of LC i just see the old information, but not

Re: WebDocMaker / Online Dictionary

No difference in the content. I made it mainly so I could have the dictionary available on my iPad in a searchable format. There is now an app available and Dash which provides the same type of thing. Thanks, Brian On Jul 4, 2018, 8:41 PM -0400, Michel F. Lukawecki via use-livecode , wrote

Re: WebDocMaker / Online Dictionary

Hi all. Being a newbie, I’m easily confused. Brian, is there a difference between your “online version of the dictionary to the LC 9.0 release” and what I find at Livecode Community/Contents/Tools/Documentation/pdf/LiveCode User Guide (9.0.0)? Thanks! Michel F. Lukawecki

WebDocMaker / Online Dictionary

I've finally updated my online version of the dictionary to the LC 9.0 release. In the process, I've posted the stack to my GitHub repo. https://github.com/bwmilby/lc-misc/tree/master/WebDocMaker The dictionary is available at: https://milby.us/lc/docs/api.html The guides are av

Re: LC 9 Dictionary, Linux

Linux") and ($LIVECODE_USE_CEF is 0) *end* revIDEBrowserWidgetUnavailable probably the easiest way to force the Dictionary opening in a stack is to change this handler to return false: *function* revIDEBrowserWidgetUnavailable * return* false *end* revIDEBrowserWidgetUnavailable Hope

Re: LC 9 Dictionary, Linux

On 06/27/2018 12:17 PM, Warren Samples via use-livecode wrote: On 06/27/2018 03:45 AM, panagiotis merakos wrote: > If your Linux machine is not affected by this issue, then you can do the following to open the Dictionary in a LC stack (as it used to be): > > 1. in the msg box ty

Re: LC 9 Dictionary, Linux

On 06/27/2018 03:45 AM, panagiotis merakos wrote: > If your Linux machine is not affected by this issue, then you can do the following to open the Dictionary in a LC stack (as it used to be): > > 1. in the msg box type "put 1 into $LIVECODE_USE_CEF" > 2. open the dictiona

Re: LC 9 Dictionary, Linux

Hi Warren, We made this "hack" to open the Dictionary in a browser as a workaround to the problem where some Linux distros could not display the browser widget. If your Linux machine is not affected by this issue, then you can do the following to open the Dictionary in a LC stack (as

Re: LC 9 Dictionary, Linux

On 06/23/2018 07:05 PM, Warren Samples via use-livecode wrote: Hello, I don't recall off the top of my head what the current remaining issue is with the dictionary under Linux. I know there have been a couple or three that have been reported by different people on different distros.

LC 9 Dictionary, Linux

Hello, I don't recall off the top of my head what the current remaining issue is with the dictionary under Linux. I know there have been a couple or three that have been reported by different people on different distros. The workaround to open the dictionary in a browser is working p

Re: Dictionary Entry For TouchMove

PR submitted to clarify the touchMove dictionary entry: https://github.com/livecode/livecode/pull/6413 On Mon, Mar 12, 2018 at 5:24 PM, Brian Milby wrote: > Short answer, you need to track the location of each touch yourself and do > the math. > > Check out this piece of c

Re: Dictionary Entry For TouchMove

and turn them on, "mid-swipe" > > simply: how do you know if touchMove is a horizontal or vertical swipe? > > in the dictionary, it says (another cryptic entry!) > > touchMove pTouchID, pTouchX, pTouchY > > Summary > > Sent when the point at which the user is to

Dictionary Entry For TouchMove

ou know if touchMove is a horizontal or vertical swipe? in the dictionary, it says (another cryptic entry!) touchMove pTouchID, pTouchX, pTouchY Summary Sent when the point at which the user is touching the screen changes. Example on touchMove pTouchID, pX, pY if pX > lastX then -- user

Re: New Books/Dictionary

This sounds like a good LCG multi-part project - building a mobile app version of the dictionary that you can mark up similar to the way you can mark up pdf's and images. Maybe you have a paint/draw layer that overlays the dictionary for notes, illustrations, etc. On Mon, Nov 27, 2017 at 1:

New Books/Dictionary

James Hale wrote: > For those wanting to read the docs in an i-device > Dash for iOS is FREE. > I have posted some screenshots on the forum > if you want to see how the docs look. > http://forums.livecode.com/viewtopic.php?f=16&t=29745&p=160713#p160712 Really nice! Thanks a lot for posting these

Re: New Books/Dictionary

Amazing, Thanks James Sean Cole *Pi Digital Productions Ltd* www.pidigital.co.uk +44(1634)402193 +44(7702)116447 'Don't try to think outside the box. Just remember the truth: There is no box!' 'For then you realise it is not the box you are trying to look outside of, but it is yourself!' eMail Ts

Re: New Books/Dictionary

For those wanting to read the docs in an i-device Dash for iOS is FREE. I have posted some screenshots on the forum if you want to see how the docs look. http://forums.livecode.com/viewtopic.php?f=16&t=29745&p=160713#p160712

Re: New Books/Dictionary

While I use the internal dictionary (via TinyDict) for quick lookups, there is something nice about having a separate browsable copy on my iPad. Why would I like an electronic version? 1. I can easily make notes, bookmarks and highlights for future reference. 2. I can browse through it on a

Re: New Books/Dictionary

For those wanting an electronic version of the dictionary download Dash (for Mac) or one of its widows or android equivalents and the Dash docset version of the docs. They are at lc9dp10 version and will be updated to dp11 soon after it is released. Searching is very fast, even with the guides

New Books/Dictionary

Greg Miller wrote: > Will it be possible to buy electronic versions of > the new dictionary and lessons book? Ideally, in a near future, lessons and dictionary would be available as interactive stacks or downloadable apps. Until then, here is a LiveCode 4.6 PDF dictionary, uploa

Re: New Books/Dictionary

Dunno about that: I use the LiveCode dictionary that I got through the Android store for nix on my cheap-N-nasty Android tablet :) Richmond. On 25/11/17 7:34 pm, Pi Digital via use-livecode wrote: Coz it sucks at searching for one thing! For another, it’s nice to have it on a device to the

Re: New Books/Dictionary

Are you just talking about the lack of full text search? The dictionary seems to work ok on my iPad (served from my server). CSS and HTML need more tweaks to work well on a phone sized device. On Sat, Nov 25, 2017 at 11:34 AM Pi Digital via use-livecode < use-livecode@lists.runrev.com>

Re: New Books/Dictionary

ov 2017, at 16:19, Richmond Mathewson via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Why would anyone want to buy an electronic version of the new dictionary > > when it comes rolled into every version of Livecode? > > > > Richmond. > &

Re: New Books/Dictionary

for inclusion with LC as the current one is tiresome. #therehastobeabetterway Sean Cole Pi Digital > On 25 Nov 2017, at 16:19, Richmond Mathewson via use-livecode > wrote: > > Why would anyone want to buy an electronic version of the new dictionary > when it comes rolled into e

Re: New Books/Dictionary

Why would anyone want to buy an electronic version of the new dictionary when it comes rolled into every version of Livecode? Richmond. On 25/11/17 5:24 pm, pink via use-livecode wrote: Will it be possible to buy electronic versions of the new dictionary and lessons book? - --- Greg

New Books/Dictionary

Will it be possible to buy electronic versions of the new dictionary and lessons book? - --- Greg (pink) Miller mad, pink and dangerous to code -- Sent from: http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html ___ use

Re: Expanded dictionary in LC 9

On 2017-10-06 09:41, James At The Hale via use-livecode wrote: I knew there was work behind the scenes with the documentation but not to this extent. While reinstating some formatting on the make docset stack I discovered than under LC 8.2 and below an enquiry to the dictionary yields 3940

Expanded dictionary in LC 9

I knew there was work behind the scenes with the documentation but not to this extent. While reinstating some formatting on the make docset stack I discovered than under LC 8.2 and below an enquiry to the dictionary yields 3940 entries In LC 9 dp9 the same enquiry yields 5646. A quick look

Re: Printed dictionary (was Re: send mouseup to control)

e format of its >> contents. > > ...this morning the printed dictionary arrived! 🎉 > > So I looked up executionContexts > > Where I read... > '' A common use of the executionContexts is to obtain the name of the > object and handler that called the current

Re: Printed dictionary (was Re: send mouseup to control)

James Hale wrote: > In following them discussion on execution contexts Richard wrote: >> The executionContexts is documented, though in all fairness that >> Dict entry includes a note about not relying on the format of its >> contents. > > ...this morning the pri

Printed dictionary (was Re: send mouseup to control)

I am reading this email (and nearly all others) on my iPad I cannot use the online dictionary as it can't handle a touch interface (the mothership is aware that they do have a non mobile friendly resource for a mobile capable product). But this morning the printed dictionary arrived! 🎉

Re: Dictionary entry for 'answer' - something missing?

gt; -- > > On Fri, May 12, 2017 at 1:31 PM, Graham Samuel via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> Maybe I don’t understand how to access the LC Dictionary in 8.1.4 rc 1, >> but when I look up ‘answer’ I miss the plain vanilla version, as

Re: Dictionary entry for 'answer' - something missing?

code < use-livecode@lists.runrev.com> wrote: > Maybe I don’t understand how to access the LC Dictionary in 8.1.4 rc 1, > but when I look up ‘answer’ I miss the plain vanilla version, as in > > answer question “Do you agree?” with “Yes” or “No” titled “Make a > Decision!” >

Dictionary entry for 'answer' - something missing?

Maybe I don’t understand how to access the LC Dictionary in 8.1.4 rc 1, but when I look up ‘answer’ I miss the plain vanilla version, as in answer question “Do you agree?” with “Yes” or “No” titled “Make a Decision!” This does work from the message box. Can anyone find this definition? If

Re: Community Dictionary (was Re: Delete element from array)

ad is http://forums.livecode.com/viewtopic.php?f=67&t=28731&p=151678#p151678 On Mon, Jan 30, 2017 at 9:10 PM, Mike Kerner wrote: Also, over there, I have included a list of bug reports that I found that seem to be relevant. If you have submitted a bug report for *the way the dictionary works*

Re: Community Dictionary (was Re: Delete element from array)

relevant. If you have submitted a bug report for *the way the > dictionary works* (not for an entry being incorrect or requiring > modification, because that is a separate, but eventually related project), > please weigh in so we can add it to the list. > > On Mon, Jan 30, 2017 at 1

Re: Community Dictionary (was Re: Delete element from array)

Also, over there, I have included a list of bug reports that I found that seem to be relevant. If you have submitted a bug report for *the way the dictionary works* (not for an entry being incorrect or requiring modification, because that is a separate, but eventually related project), please

  1   2   3   4   >