Re: Array glitch

Peter- Friday, July 12, 2013, 4:42:02 PM, you wrote: > OK, all works fine for me too on a Mac so it does look like it's a Windows > problem (maybe Linux too?) No problem here on linux (32-bit or 64-bit). -- -Mark Wieder mwie...@ahsoftware.net ___

Re: Array glitch

OK, all works fine for me too on a Mac so it does look like it's a Windows problem (maybe Linux too?) Pete lcSQL Software On Fri, Jul 12, 2013 at 3:54 PM, Mark Wieder wrote: > Pete- > > Friday, July 12, 2013, 12:39:51 PM, you wrote: > > > Just to confirm, you can get int

Re: Array glitch

Pete- Friday, July 12, 2013, 12:39:51 PM, you wrote: > Just to confirm, you can get into the debugger variables tab and expand the > array to show its key and value? Yep. That was my test case. Hit the breakpoint, drop down to the variables tab, expand the array, see the zero. And the seconds. D

Re: Array glitch

Just to confirm, you can get into the debugger variables tab and expand the array to show its key and value? Pete lcSQL Software On Fri, Jul 12, 2013 at 11:23 AM, Mark Wieder wrote: > Mark- > > Friday, July 12, 2013, 9:56:18 AM, I wrote: > > > Aha! A second confirmation.

Re: Array glitch

Mark- Friday, July 12, 2013, 9:56:18 AM, I wrote: > Aha! A second confirmation. Maybe it's just a Windows thing? Still works for me here on OSX 10.6 with LC 4.6.4, 5.5.3, and LC Community 6. -- -Mark Wieder mwie...@ahsoftware.net ___ use-livecode

Re: Array glitch

Pete- Friday, July 12, 2013, 10:06:34 AM, you wrote: > Could be - my Mac is in hospital having hard drive replacement surgery so > can't test on OSX right now. Ouch! That's right - I forgot about that. Hope it won't be long. -- -Mark Wieder mwie...@ahsoftware.net ___

Re: Array glitch

Could be - my Mac is in hospital having hard drive replacement surgery so can't test on OSX right now. Pete lcSQL Software On Fri, Jul 12, 2013 at 9:56 AM, Mark Wieder wrote: > Pete- > > Friday, July 12, 2013, 9:21:46 AM, you wrote: > > > Terry, > > I tried your script h

Re: Array glitch

Pete- Friday, July 12, 2013, 9:21:46 AM, you wrote: > Terry, > I tried your script here and got the same error as you in LC 5.5.4 and LC > Community 6.0 on a Windows 8 box. Aha! A second confirmation. Maybe it's just a Windows thing? -- -Mark Wieder mwie...@ahsoftware.net __

Re: Array glitch

Terry, I tried your script here and got the same error as you in LC 5.5.4 and LC Community 6.0 on a Windows 8 box. I use strict compile mode but declaring the tSimpleArray variable made no difference. I also put the seconds into a variable, tKey, put zero into tSimpleArray[tKey], then did a put t

Re: Array glitch

Terry Dennis wrote: ? >-- It ONLY occurs when I try to display the array in the debugger. It >*appears* programmatic access is fine. Since it works okay for everyone at runtime, and it only crashes for you in the debugger, I'd think the problem is with the debugger. If that's true then keep

Re: Array glitch

Mark: re: test script in a button in a *new stack*? Been there, done that. As I noted in a prior email, it occurred ... "3) in an entirely new stack after exiting and re-entering LC" Perhaps I'm being paranoid and I shouldn't worry about it. If I rely on that assumption as a basis for using s

Re: Array glitch

Terry- Thursday, July 11, 2013, 5:19:46 PM, you wrote: > Does this occur with typing in a whole new script with no cut and paste? > -- YES. That’s how I created the test script. I manually typed it into a new > button’s mouseUp script. How about that test script in a button in a *new stack*? My

Re: Array glitch

Does this occur if you dump the array (using your favorite method)? -- NO. All other accesses to the array *appear* to work fine. Of course, I haven’t tested *every* possible value. Does this occur with just the breakpoint? -- It occurs with either a manually applied breakpoint, or a coded bre

Re: Array glitch

how do I determine what caused this? > > Terry > > From: Mark Wieder > To: use-livecode@lists.runrev.com > Subject: Re: Array glitch > Message-ID: <16481125456.20130711150...@ahsoftware.net> > Content-Type: text/plain; charset=us-ascii > > Jacque- > >

Re: Array glitch

Oh, what I meant was that maybe there was something weird in the variable. On Jul 11, 2013, at 4:58 PM, Mark Wieder wrote: > Dar- > > Thursday, July 11, 2013, 3:20:04 PM, you wrote: > >> I wonder if tSimpleArray is really global or scriptLocal. > > I tried it all three ways and it still worked

Re: Array glitch

... how do I determine what caused this? Terry From: Mark Wieder To: use-livecode@lists.runrev.com Subject: Re: Array glitch Message-ID: <16481125456.20130711150...@ahsoftware.net> Content-Type: text/plain; charset=us-ascii Jacque- Thursday, July 11, 2013, 2:07:04 PM, you wrote: What

Re: Array glitch

Dar- Thursday, July 11, 2013, 3:20:04 PM, you wrote: > I wonder if tSimpleArray is really global or scriptLocal. I tried it all three ways and it still worked for me. Maybe it was triggered in between seconds like that Damon Knight story... -- -Mark Wieder mwie...@ahsoftware.net ___

Re: Array glitch

I wonder if tSimpleArray is really global or scriptLocal. OK, not likely. Sometimes weird characters sneak into scripts. Maybe the crash dump has a clue. Dar On Jul 11, 2013, at 4:03 PM, Mark Wieder wrote: > Jacque- > > Thursday, July 11, 2013, 2:07:04 PM, you wrote: > >> What's the bug

Re: Array glitch

Jacque- Thursday, July 11, 2013, 2:07:04 PM, you wrote: > What's the bug exactly? Big numbers as keys? Oops. I can't find the bug I was thinking about at the moment, but it turns out I was thinking of another reported bug. I tried the test script here and it worked fine. -- -Mark Wieder mwie

Re: Array glitch

On 7/11/13 2:26 PM, Mark Wieder wrote: Terry- Thursday, July 11, 2013, 12:12:32 PM, you wrote: -- How do I find out what caused this? Is there a limitation on the size of a numeric key? It's a known bug with the built-in debugger. What's the bug exactly? Big numbers as keys? -- Jacqueli

Re: Array glitch

Terry- Thursday, July 11, 2013, 12:12:32 PM, you wrote: > -- How do I find out what caused this? Is there a limitation on the size of > a numeric key? It's a known bug with the built-in debugger. PowerDebug: http://powerdebug.ahsoftware.net http://www.ahsoftware.net/PowerTools/BuyPowerDebug.i