LiveCode Forums.

I noticed that LC8 and LC 7 share the same "My Livecode" user extension folder.
Before (5.5) I could have different extension folder according to the LC version.
Very strange indeed since the folder content for the two version must be different.

May be they share preferences too since, for example, on the Standalone Application Setting, now that I have LC8 installed, is possible to set the standalone for OS X, Windows AND iOS (before was either iOS or desktop).

Can someone confirm this ? (a nuisance for me since I have to update preferences when I open another version.

Trevix

LC v7 is no longer being maintained now that v8 is out. Moreover, it's generally faster than v7, and contains more than a thousands fixes and enhancements not in v7.

There may be ways to continue using both, but it may be simpler to just use the current version.

Is there anything in your projects that isn't working well in the latest build if v8? If so, let's identify that and fix it. As a superset if capabilities, v8 should ideally be a smooth upgrade from v7.

I don't mean to rant, but since I decided to pass to LC 8 with the 2 stacks I am working now, I have fund and reported many "structural" bugs. I mean no bugs due to changes in the language, but fundamental things that don't work anymore.
Panos has been of great help. You can see all my reports under "trevix".
I understand the complexity and I admire the LC people, but I think the foundation of LC8 are not ready yet for a full cycle of development (the project browser, crash after standalone saving, screen refresh, tabs drawing, script execution stopping without warning, etc). 50 % of my time is now dedicated to find out why the stacks work on 7 and not as well on 8.

Sorry
Trevix

Once in a while I've come across fixed in v8 that expose bugs in v7 and earlier, and some of those have caused script errors where no error was reporting previously. Hard to say if that's true for the issues you reported, but since LC 8 is the currently-maintain it seems worth spending more time there since anything in v7 or earlier will ultimately stop working at some point as OSes change.

I took at look at your outstanding reports in the DB (thanks for submitting those), and it looks like one of those has been fixed, another confirmed with notes of fixes to related issues that may merit re-testing, and three of those are awaiting response from you. The rest appear to have been reported against v7, so unless you're seeing those in v8 they may have already been fixed, and of course will continue to affect any work done in v7 even if they're fixed in the current version.

I saw that one of your bugs was reported against the current version (8.1 RC2), among those awaiting follow-up. The others were reported against earlier v8.x builds.

You're right that v8 is one of the most substantial upgrades to LC ever, and as we see with a lot of other software, even operating systems, the first point release after offers an opportunity to refine implementation as more people begin using it.

v8.1 is that point release, and being RC 2 this is the best time to make sure anything that needs fixing gets done.

Please let me know if there are any of the "Awaiting Follow-up" items I may be able to help triage.