LiveCode Forums.

Describe what you need, and one of us can write a function for that in a few minutes. If you want to write it yourself see either lineOffset or offset, noting the placeholder variable (linesToSkip or charsToSkip) from the description.

richmond62 wrote: Sun Oct 04, 2026 5:10 pm ... those versions have been available for less than a week.

Thanks. Early to expect finished apps. But how are the app ecosystems for Haiku or Mac PPC? What does the demand side of those app economies look like?

richmond62 wrote: Fri Oct 02, 2026 7:49 pm At the moment OXTL7 (derived from LC 7.1.4 community) can ONLY run and deliver standalones on Haiku OS, UNIX, and Steam, MacOS PPC...

How many applications have been made with those versions?

dunbarx wrote: Wed Sep 16, 2026 2:53 pm Hmmm, again.

I am Mac only. Is this real?

If it exists and is made in LiveCode, I'm curious about what could make a script editor "Windows-only".

A script-only stack contains only the script of the stack.

Is LiveCode still alive?

Just about any small business owner can monitor and engage with their social media audience, across venues they own and public platforms as well, in just about 1 hour each week.

I do not understand why any business owner would not do that.

If they did, the visible ...

dunbarx wrote: Wed Jul 29, 2026 4:49 am I do not understand why the dictionary does not hold the entirety of the lexicon, even if there were a few filters to separate the several types into groups.

Technically, those aren't LC variables. They're provided by the OS, and may vary from system to system, and sometimes between OS versions.

Consider using load with callbacks.
https://lessons.livecode.com/m/4071/l/7 ... o-livecode

Callbacks keep network I/O clean and efficient.

gregward74 wrote: Wed May 27, 2026 8:47 pm For what it's worth, I don't think this announcement means Classic is ending.

Yes and no.

The maintenance of a separate installation for 10 is going away sometime in 2027.

The Classic IDE remains supported as an option in the v11 package.

Hard to follow the block of text. A simple example stack exhibiting the issue will help us resolve it in seconds. I suspect it has to do with variable names quoted in a way that causes them to be seen instead as strings, but I'm just guessing. An example stack will turn guessing into a solution ...

The scripting language is there, the Classic IDE is needed to build Create, many of the bug reports make reference to using Classic.

At the end of the day, you can build the Create IDE in Classic (indeed, that's what they're doing), but not the other way around.

I see Classic as a less attractive ...

My understanding is that sometime next year the current engine will cease getting support and updates. It should continue to work, but if any supported OS changes there will be no fixes after Classic is discontinued. I'm not clear on how current licenses will be managed.

Yes, the engine path ...

continue using it as the workshop where Create is worked on

The company may do that: but whether they are going to continue licensing it to others is another question.

What conjecture about any future doesn't involve unknowns?

I'm just looking at the pragmatic aspects from a business owner ...

Richard.
Classic IDE is still available as an option in Create, and I can't imagine any benefit in adding the additional expense of somehow purging it later on.

"Still available..." That seems like a tenuous hope; the effort of maintaining its compatibility with Create might either orphan it ...

Richard.

Am I somehow disingenuous in my thinking that only classic can do anything, never mind that Create can do lots of things?

I'm not sure how "disingenuous" could apply.

It's all more or less the same engine, with the biggest difference being the IDE stacks files. One of the things I've ...