LiveCode Forums.

richmond62 wrote: Sat Jan 06, 2024 3:02 pm What does 'Indy' mean?
-
Screenshot 2024-01-06 at 16.00.38.png

It means that apart from being facetious, you’re using an old IDE from the time that licences were either Community, Community Plus, Indy and Pro.

As you well know there is now only Starter plan and Standard plan.
Not quite sure what your point is, it’s not something you see with the current IDE….

It’s about as wondrous as booting up a winXP PC and posting a pic of green rolling hills asking what background that is lol

My point is that in the past there were several tiers of LC licence which did not mean a lot of people who could not afford 'top banana' were excluded.

...which did not mean a lot of people who could not afford 'top banana' were excluded.

I analyzed this using a wonderful program called "LiveCode"

It returned: "...which meant a lot of people who could afford 'top banana' were excluded".

I am working, still using that adorable program. to figure out its intent...

Craig

And what, forbye, is that just supposed to mean? And what are you ettling at?

It just seemed odd that those who could afford first class were not permitted to sit there.

Craig

That's not what he said. Paraphrasing:

There were tiers of licensing which did not mean that

people who could not afford to pay for higher tiers

would be excluded.

Or,

There were tiers which did not mean the exclusion of

those who could not afford higher tier payments



---
However, I believe that at least for the Community Edition, the open source licence terms dictated that stack encryption had to be disabled. It was never possible under open source, so in some situations some users *are* excluded from higher tier features.

One facetious post has diverted the whole thread to complaining about LC’s pricing structure instead. Again.

There is a low-cost licence that amounts to two Starbucks coffees per month, per platform. Yes, there are limitations with this. No it’s not free. But neither is it unaffordable for the vast majority.

If even that is unaffordable then go by all means use the opensource alternative and complain on their forum. Or use the old community version acknowledging that is now deprecated, and I believe is not a topic for this forum.

The realities of a free lunch not being possible have been discussed endlessly in the forums.

Also moaning about this in random threads is not going to achieve anything.
Fair enough if it’s the topic being discussed but shoehorning it in by posting a screen shot of deprecated IDE and posing facetious questions is at best unhelpful.

One facetious post

Time to look in the mirror and ask if some people are not taking things too seriously.

Richmond.

I am guilty of both instigating and prolonging this sort of nonsense. I appreciate this can be annoying in that it sidetracks the flow of actual discussion, something I am eager to participate in. This does not speak to how silly or clever any of it is.

Some people "sigh" when I, yet again, toss in rude comments about Windows. That is a character flaw of mine that I am smug about.

There is a fine line between that sigh, itself a cute and yet telling comment, and going a bit too far amongst friends.

I have said this before: "Anyone remember Amthony Black?"

Craig

This thread is about a stack already being in memory. It went off the rails at least twice, still without resolution of the original issue.

Maybe that non-closure made the thread ripe for the sophomoric nature of some of us to blossom?

Craig

I went and dug out some notes of mine from 2002, when I was working on some commercial software in Scotland with RunRev 1.1.1 or RunRev 2, and found I had a similar problem with claims that stacks were already loaded; so this is nothing particularly new.

I just wonder if, by some odd chance the destroyStack thing got 'bumped':
-

occupationwaveson wrote: Mon Jan 08, 2024 4:55 pm I'm encountering an issue when transitioning from one stack to another. A message keeps popping up, indicating that the second stack is already in memory. Despite closing and removing both stacks from memory, restarting the process doesn't resolve the problem. These are two distinct stacks, and none of them function as a substack.

I'm curious if there's a workaround to eliminate this issue, or if starting from scratch is the recommended solution. Any insights or suggestions would be greatly appreciated. Thank you!

1. Start a fresh session in LiveCode.
2. Open one of the stacks.
3. Change its name.
4. Save.

Now you no longer have two stacks with the same name.

Richard.

The OP mentioned early on that the two stacks were named "Thekey" and "hold2".

Craig

dunbarx wrote: Mon Jan 08, 2024 5:22 pm Richard.

The OP mentioned early on that the two stacks were named "Thekey" and "hold2".

Then we'll need a screen shot to see what's really happening.

We've all seen the duplicate stack name dialog, but in more than 20 years I've never seen it when there was no duplicate stack name.

The error dialog usually contains the name of the duplicate stack, which would help. Often it's the ask/answer dialogs if the stack has previously been built as a standalone.