LiveCode Forums.

Don't know if this is the right forum, but I decided to try Community 7.0 RC1, coming from 6.1.1 and 6.1.3. Standalones for all 3 platforms went from 3Mb to about 13Mb, and performance went from snappy fast to sluggish screen updates in Windows 7 and OS X. What am I doing wrong? -John

Hi jwkuehne,

coming from 6.1.1 and 6.1.3. Standalones for all 3 platforms went from 3Mb to about 13Mb

I believed understand that is the new part for unicode that takes a lot of space.
Best regard
Jean-Marc

Stay away from Livecode 7 - Unless you have a need for Unicode OR until they IMPROVE
the speed, bugs and size of the executable.

Sorry, don't mean to be negative I just think LC7 needs more time for the developers to
improve on it.



jeffe

jeffe wrote:Stay away from Livecode 7 - Unless you have a need for Unicode OR until they IMPROVE
the speed, bugs and size of the executable.

Sorry, don't mean to be negative I just think LC7 needs more time for the developers to
improve on it.

On the contrary, that's exactly why test builds like v7.0 DP10 are made available: so we can pin down any weaknesses we need addressed BEFORE release.

Waiting until after release to test just slows the whole process down, guaranteeing that if there's something you need that hasn't been addressed it can't be until the next version after.

Please submit bug reports with a recipe for any issue you find here:
http://quality.runrev.com/

Hi jwkuehne and jeffe

Maybe you didn't realise that LiveCode 7.0.0(RC1) is a 'Release Candidate' version of LiveCode? The following is from LiveCode's website and explains what 'RC' is in context:

STABLE - These releases are stable public releases.
RC - Short for "Release Candidate", these releases are feature complete and have been made public to allow LiveCode developers to test whether they think the release is stable. Users who find bugs can file them at http://quality.runrev.com.
DP - Short for "Developer Preview", these releases are not feature complete and likely to contain bugs. They have been made public to allow LiveCode developers to experiment with the latest features and feedback to the team. Users who find bugs can file them at http://quality.runrev.com.

So as you can see, Richard is absolutely right in that we should all really pitch in to test 'DP' and 'RC' versions of LiveCode so that we can all have stable versions of LiveCode - but also - we should all be careful of what versions of LiveCode we are using at any particular time, for example, it would be a brave programmer who tried submitting an app built with an 'RC' build of LiveCode...

Kind regards

Dave