Re: problems with 5.5, 6.6, 6.7. 7.0

2014-12-29 Thread Bernard Devlin
Thanks for the suggestion Bill.  However, I don't see how it can be
something to do with the disk.

In the case of 5.5, the border of an image disappears when the blendLevel
is altered.  This seems to have something do with the new layerMode
introduced in 5.5.

With regard to the 6.x series, I hadn't been doing any LC development
between June and the end of November.

I remembered last night that I'd seen that distinctive visual artefact, of
the clock moving from the start bar to the to top left of the screen, so I
checked back on my notes.  When I looked back on my notes, I found that I
got these crashes when I tried out 6.6.  In April I was working on an
entirely different kind of stack (no use of images or graphics).  My notes
show that 6.6 would hang/crash in just these unpredictable ways (even just
deleting a line in the script editor would cause these kinds of problems).
It seems that on Window 7, 6.7 still has these unpredictable problems.
I've been using this particular PC for a couple of years, with no other
application but Livecode behaving in this erratic manner.

5.5 was at least very stable while I was doing nothing with images (i'd
been using the 5.x series on this PC from 2011 until I tried 6.6 in
April).  With 6.6 and 6.7 it seems extremely unstable, regardless of what I
am doing.  I realise that others are recommending 6.6 to those with
problems with 7.0.  However, since no-one has drawn attention to the visual
inconsistencies with a scrolling field on Windows (see the bug report I
mentioned), I'm wondering if very few people are using LC on Windows.
Either that or there's some strange incompatibility between LC 6.x and my
PC.  I've checked the graphics drivers and there's nothing more up to date
than what's installed.

Regards, Bernard



On Sun, Dec 28, 2014 at 10:35 PM, EED-wp Email proth...@earthednet.org
wrote:

 Bernard
 Don't know if this will help, but when I get this kind of inexplicable
 failure sequence, I start by rebuilding, testing the system disc drive. I'm
 on OS X and. LOVE Disk Warrior. It fixes disc corruption problems the the
 Disk Utility reports as unfixable. Don't know about Windows os's.

 Regards and good luck.
 Bill

 William Prothero
 http://ed.earthednet.org

  On Dec 28, 2014, at 9:53 AM, Bernard Devlin bdrun...@gmail.com wrote:
 
  I'm having problems with every version of Livecode I've tried using in
 the
  past month or so.
 
  On 5.5 I get a crash with an image when I use the inspector to look at
 the
  colors/patterns.  So I started to use 7.0 a few weeks ago, but went down
 to
  6.6 and 6.7 when I got a corrupted stack with 7.0.
 
  On 6.6 and 6.7 I am getting random hangs (this is with a different stack
 to
  the one where I have problems in 5.5).  I cannot find any pattern to
 these
  hangs.  Even trying to close Livecode 6 using task manager is a problem:
 it
  can take several attempts, and much of the screen area not occupied by
  Livecode becomes distorted/unresponsive (for example, the clock moves
 from
  the bottom right hand side of the screen where the taskbar is, to the top
  left of the screen)
 
  On 7.0 I had a corrupted stack (and since the stack file is different in
  7.0, I'm very wary about continuing to use that version).
 
  6.7 and 7.0 also have basic defects when it comes to the field object.
  http://quality.runrev.com/show_bug.cgi?id=14222.  I'd been using 5.5 and
  only recently started to use 6.7 and 7.0.  I'm surprised no-one else
  reported the defects with the scrolling field on Windows (I'm assuming
 they
  are not confined to my copy of Windows, since runrev have acknowledged
 the
  bug as New).
 
  These problems are all occurring on Windows 7.
 
  Are there crash logs I can send to runrev?  I have no recipe whatsoever
 for
  the problems with 6.x
 
  Bernard
  ___
  use-livecode mailing list
  use-livecode@lists.runrev.com
  Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
  http://lists.runrev.com/mailman/listinfo/use-livecode

 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: problems with 5.5, 6.6, 6.7. 7.0

2014-12-29 Thread Richmond

On 29/12/14 11:16, Bernard Devlin wrote:

Thanks for the suggestion Bill.  However, I don't see how it can be
something to do with the disk.

In the case of 5.5, the border of an image disappears when the blendLevel
is altered.  This seems to have something do with the new layerMode
introduced in 5.5.

With regard to the 6.x series, I hadn't been doing any LC development
between June and the end of November.

I remembered last night that I'd seen that distinctive visual artefact, of
the clock moving from the start bar to the to top left of the screen, so I
checked back on my notes.  When I looked back on my notes, I found that I
got these crashes when I tried out 6.6.  In April I was working on an
entirely different kind of stack (no use of images or graphics).  My notes
show that 6.6 would hang/crash in just these unpredictable ways (even just
deleting a line in the script editor would cause these kinds of problems).
It seems that on Window 7, 6.7 still has these unpredictable problems.
I've been using this particular PC for a couple of years, with no other
application but Livecode behaving in this erratic manner.

5.5 was at least very stable while I was doing nothing with images (i'd
been using the 5.x series on this PC from 2011 until I tried 6.6 in
April).  With 6.6 and 6.7 it seems extremely unstable, regardless of what I
am doing.  I realise that others are recommending 6.6 to those with
problems with 7.0.  However, since no-one has drawn attention to the visual
inconsistencies with a scrolling field on Windows (see the bug report I
mentioned), I'm wondering if very few people are using LC on Windows.
Either that or there's some strange incompatibility between LC 6.x and my
PC.  I've checked the graphics drivers and there's nothing more up to date
than what's installed.

Regards, Bernard






My inclination would be to try all these versions out on another PC 
running the same version of Windows you are
using at the moment: if you can repeat these effects then it is 
Livecode: if not, it's your machine.


Richmond.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


problems with 5.5, 6.6, 6.7. 7.0

2014-12-28 Thread Bernard Devlin
I'm having problems with every version of Livecode I've tried using in the
past month or so.

On 5.5 I get a crash with an image when I use the inspector to look at the
colors/patterns.  So I started to use 7.0 a few weeks ago, but went down to
6.6 and 6.7 when I got a corrupted stack with 7.0.

On 6.6 and 6.7 I am getting random hangs (this is with a different stack to
the one where I have problems in 5.5).  I cannot find any pattern to these
hangs.  Even trying to close Livecode 6 using task manager is a problem: it
can take several attempts, and much of the screen area not occupied by
Livecode becomes distorted/unresponsive (for example, the clock moves from
the bottom right hand side of the screen where the taskbar is, to the top
left of the screen)

On 7.0 I had a corrupted stack (and since the stack file is different in
7.0, I'm very wary about continuing to use that version).

6.7 and 7.0 also have basic defects when it comes to the field object.
http://quality.runrev.com/show_bug.cgi?id=14222.  I'd been using 5.5 and
only recently started to use 6.7 and 7.0.  I'm surprised no-one else
reported the defects with the scrolling field on Windows (I'm assuming they
are not confined to my copy of Windows, since runrev have acknowledged the
bug as New).

These problems are all occurring on Windows 7.

Are there crash logs I can send to runrev?  I have no recipe whatsoever for
the problems with 6.x

Bernard
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: problems with 5.5, 6.6, 6.7. 7.0

2014-12-28 Thread EED-wp Email
Bernard
Don't know if this will help, but when I get this kind of inexplicable failure 
sequence, I start by rebuilding, testing the system disc drive. I'm on OS X 
and. LOVE Disk Warrior. It fixes disc corruption problems the the Disk Utility 
reports as unfixable. Don't know about Windows os's. 

Regards and good luck. 
Bill

William Prothero
http://ed.earthednet.org

 On Dec 28, 2014, at 9:53 AM, Bernard Devlin bdrun...@gmail.com wrote:
 
 I'm having problems with every version of Livecode I've tried using in the
 past month or so.
 
 On 5.5 I get a crash with an image when I use the inspector to look at the
 colors/patterns.  So I started to use 7.0 a few weeks ago, but went down to
 6.6 and 6.7 when I got a corrupted stack with 7.0.
 
 On 6.6 and 6.7 I am getting random hangs (this is with a different stack to
 the one where I have problems in 5.5).  I cannot find any pattern to these
 hangs.  Even trying to close Livecode 6 using task manager is a problem: it
 can take several attempts, and much of the screen area not occupied by
 Livecode becomes distorted/unresponsive (for example, the clock moves from
 the bottom right hand side of the screen where the taskbar is, to the top
 left of the screen)
 
 On 7.0 I had a corrupted stack (and since the stack file is different in
 7.0, I'm very wary about continuing to use that version).
 
 6.7 and 7.0 also have basic defects when it comes to the field object.
 http://quality.runrev.com/show_bug.cgi?id=14222.  I'd been using 5.5 and
 only recently started to use 6.7 and 7.0.  I'm surprised no-one else
 reported the defects with the scrolling field on Windows (I'm assuming they
 are not confined to my copy of Windows, since runrev have acknowledged the
 bug as New).
 
 These problems are all occurring on Windows 7.
 
 Are there crash logs I can send to runrev?  I have no recipe whatsoever for
 the problems with 6.x
 
 Bernard
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your subscription 
 preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode