Re: arrayencode

Martin Koob wrote: > What is LSON? A web search doesn’t turn up anything. A shot > in the dark here but Is it something internal to LiveCode i.e. > Livecode Script Object Notation that is the basis for LiveCode > arrays? Sorry, Martin. I need to get out more. I've been using LSON ("LiveCode

Re: arrayencode

What is LSON? A web search doesn’t turn up anything. A shot in the dark here but Is it something internal to LiveCode i.e. Livecode Script Object Notation that is the basis for LiveCode arrays? Thanks for the references on BSON Martin > On Jun 21, 2022, at 10:43 PM, Richard Gaskin via use-l

Re: arrayencode

l oTom Glod wrote: > I am wondering if anyone here knows the encoding algorithm > that arrayencode() uses? Yes. > Is it one that can be implemented in another language or is > it proprietary? It should be technically possible to implement any algo in any sufficiently-complete language. Whe

Re: my keyUp message has disappeared

I neglected to write the modified “keyUp” handler I am now using when I posted. it should read: > on keyUp x > answer x & random(99) > end keyUp in order to get that “x56” I mentioned. Craig > On Jun 21, 2022, at 2:16 PM, Craig Newman via use-livecode > wrote: > > This is summarized from

my keyUp message has disappeared

This is summarized from a couple of threads in the forum: - The "keyUp"message has disappeared. This happened to me once before, several weeks ago, and trashing the prefs file fixed it. But now even that does not cut it. So a new stack in a new s

arrayencode

Hi Folks, I am wondering if anyone here knows the encoding algorithm that arrayencode() uses? Is it one that can be implemented in another language or is it proprietary? Thanks, Tom ___ use-livecode mailing list use-livecode@lists.runrev.com Please vis

Re: M1 Macs and LC 9.6.8 RCs and 10.0.0 RCs

> Am 21.06.2022 um 15:19 schrieb Mark Waddingham via use-livecode > : > > On 2022-06-21 12:18, matthias rebbe via use-livecode wrote: >>> Am 21.06.2022 um 11:56 schrieb Mark Waddingham via use-livecode >>> : >>> Why? >> First, it's more convenient for the developer. > > I think the end user

Re: M1 Macs and LC 9.6.8 RCs and 10.0.0 RCs

On 2022-06-21 12:18, matthias rebbe via use-livecode wrote: Am 21.06.2022 um 11:56 schrieb Mark Waddingham via use-livecode : Why? First, it's more convenient for the developer. I think the end user is more important (in this case) ;) The Intel only and Apple only builds are smaller ins s

Re: OT Re: Referencing Livecode

Hi. These are great examples of use cases for LiveCode and it is great how you explain the app design. It especially cool that the apps are used for citizen science. It complements LiveCode's “anyone can code” tag line with the “any one can do science" ethic of citizen science. Thanks Alan.

Re: M1 Macs and LC 9.6.8 RCs and 10.0.0 RCs

> Am 21.06.2022 um 11:56 schrieb Mark Waddingham via use-livecode > : > > On 2022-06-20 20:55, matthias rebbe via use-livecode wrote: >> Anyway, the macOS Apple support is currently experimental, i am pretty >> sure there will be such an option in future. At least i hope so. ;) > > Why? > F

OT Re: Referencing Livecode

That is really helpful Alan. A pair of fine papers! I visited Australia & NZ a few years back and started using iNaturalist and then the Seek app, so I’m now an enthusiastic CS observation reporter. Cheers, David G > On 21 Jun 2022, at 12:46 am

Re: M1 Macs and LC 9.6.8 RCs and 10.0.0 RCs

On 2022-06-20 20:55, matthias rebbe via use-livecode wrote: Anyway, the macOS Apple support is currently experimental, i am pretty sure there will be such an option in future. At least i hope so. ;) Why? The idea of universal binaries is to ensure that a single app/installer can be shipped to

Re: Referencing Livecode

Alan Stenhouse via use-livecode wrote > In a couple of my publications, I described developing apps with Livecode and > referred to www.livecode.org and www.livecode.com, but didn't include > anything > in the references as there was nothing (AFAICS at that time) that would > satisfy > scient