hair-pulling frustration

[Richard Gaskin]

Dr. Hawkins wrote:

> On Tue, Nov 11, 2014 at 4:38 PM, Richard Gaskin wrote:
> 
>> Any other specific issues you feel are show-stoppers may well be worth
>> looking into, and I'd be happy to help if I can.  But to do that I'd 
>> need
>> to know what they are.
>> 
> 
> That the IDE doesn't work?

I'll run a search for "IDE doesn't work" and see what I can come up 
with. ;)


> I filed those bugs, but can anyone really have used the IDE and 
> breakpoints
> without noticing the hangs, and the inability to set these?

Thanks for noting which bugs were concerning you.

The one I had referred to was about the card reference, which has 
already been fixed:
http://quality.runrev.com/show_bug.cgi?id=13972


For those following this the breakpoint bugs are:
http://quality.runrev.com/show_bug.cgi?id=13997
http://quality.runrev.com/show_bug.cgi?id=13998
http://quality.runrev.com/show_bug.cgi?id=13999

I did a quick triage on those:

The first one ('97) was especially interesting because in all the years 
I'd been using LC I'd never used that particular feature.  The 
description of that feature on p68 of the User Guide does seem to match 
your expectations, and I was able to confirm your report.

The second one ('98) was one that could benefit from others here who've 
used the debugger more than I have (Jacque, that means you <g>).  I'm 
not sure if it's a bug or merely needs more explanation in the docs.

The last one ('99) I was unable to reproduce, but if there are any 
additional steps I can follow to reliably reproduce I'd be happy to 
submit my notes there.


> And how many years has it been since a current version can watch a 
> global
> variable without crashing? or the false failures to compile over 
> shadowed
> names?

Bug #s?

Anyone else experience those?

There was a recent comment about shadowed name warnings in the Facebook 
group recently, but that seemed related to turning on the feature to 
warn about those (Prefs -> Script Editor -> Strict Compilation Mode).  
The person who noted the issue reported back that after restoring that 
feature to its default "off" setting he was happy.  Is that not working 
for you?

-- 
  Richard Gaskin
  LiveCode Community Manager
  richard at livecode.org