I have been using Livecode 6.6.2 Stable Community on a number of computers running a variety of Debian derivative Linuxes
in my school for the last 3 weeks, and continually encounter a problem where the revToolbar stack suddenly becomes transparent:
So "Stable" may be a bit inaccurate.
6.6.2 Stable not what it could be
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Livecode Opensource Backer
- Posts: 9454
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
-
- VIP Livecode Opensource Backer
- Posts: 327
- Joined: Sun Apr 15, 2012 1:17 am
- Location: USA
- Contact:
Re: 6.6.2 Stable not what it could be
I have been using it too in my classes but on Windows 7 computers and have seen the same problems.
And other minor and inconsistent problems but nothing to capture or document enough to send in.
And other minor and inconsistent problems but nothing to capture or document enough to send in.
Cyril Pruszko
https://sites.google.com/a/pgcps.org/livecode/
https://sites.google.com/a/setonhs.org/app-and-game-workshop/home
https://learntolivecode.com/
https://sites.google.com/a/pgcps.org/livecode/
https://sites.google.com/a/setonhs.org/app-and-game-workshop/home
https://learntolivecode.com/
-
- Livecode Opensource Backer
- Posts: 9454
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: 6.6.2 Stable not what it could be
Well 'Stable' should mean that all those inconsistencies and grumbles have been ironed out.
Methinks somebody has not been doing their Beta-testing quite as thoroughly as they might.
Methinks somebody has not been doing their Beta-testing quite as thoroughly as they might.
-
- VIP Livecode Opensource Backer
- Posts: 327
- Joined: Sun Apr 15, 2012 1:17 am
- Location: USA
- Contact:
Re: 6.6.2 Stable not what it could be
In all fairness, those inconsistencies and grumbles are hard to track down.
They are like memory leaks where you do not hit them until a certain threshold is reached. That is difficult because it is dependent on so many factors - what commands you do, how often, in what sequence, what OS, what memory you have, etc.
It is also hard if you can not reproduce it dependably enough to determine where in the code it is occurring.
All in all, they do a good job with the size of the engine..
They are like memory leaks where you do not hit them until a certain threshold is reached. That is difficult because it is dependent on so many factors - what commands you do, how often, in what sequence, what OS, what memory you have, etc.
It is also hard if you can not reproduce it dependably enough to determine where in the code it is occurring.
All in all, they do a good job with the size of the engine..
Cyril Pruszko
https://sites.google.com/a/pgcps.org/livecode/
https://sites.google.com/a/setonhs.org/app-and-game-workshop/home
https://learntolivecode.com/
https://sites.google.com/a/pgcps.org/livecode/
https://sites.google.com/a/setonhs.org/app-and-game-workshop/home
https://learntolivecode.com/
-
- Livecode Opensource Backer
- Posts: 9454
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: 6.6.2 Stable not what it could be
I think between Windows 7 and Ubuntu a case can be made for
not enough work being done.
This is not an odd, occasional blip; this is the 'revTools.rev' stack
throwing a wobbly almost all the time!
not enough work being done.
This is not an odd, occasional blip; this is the 'revTools.rev' stack
throwing a wobbly almost all the time!