I have noticed it, and just written it off to flakiness of RDi. There are several little things that bug me, but not enough to complain about it, and also because it is so hard for me to open a PMR. I sometimes can see the values popup, and sometimes can't. If a data structure has anonymous fields in it, the values display properly in the monitor view when the DS is added, but as soon as a value in the DS changes, everything below the first anonymous field is wrong. Monitor and Variables views get confused with scope: Variables does not always contain all "in-scope" variables, and Monitor sometimes looses track of global variables. On the plus side, if a DS with anonymous fields does appear in the variables view, all fields have the correct value, even after changes.
Apart from the debugger, there is other flakiness. Sometimes when typing after moving the cursor, the cursor skips two positions after the first character is typed. So if I have something like CHAIN RRN RECORD;, and I want to put a data structure in there after the record name, I position the cursor to just before the ';', and type ' DSNAME'. Sometimes it works properly and I end up with CHAIN RRN RECORD DSNAME;, but sometimes I get this CHAIN RRN RECORD ;DSNAME. It is relatively frequent, maybe a dozen times a day. I would like to blame my keyboard or fat fingers on this, but RDi is the only application this happens with, and it only happens after the first character typed.
I am using Windows 7 Pro SP1 64-bit, RDi 9.1.1.1
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----Buck Calabro <kc2hiz@xxxxxxxxx> wrote: -----
To: wdsci-l@xxxxxxxxxxxx
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: 08/13/2015 05:01PM
Subject: Re: [WDSCI-L] Fw: RDi stops responding during interactive debug
On 8/13/2015 3:51 PM, Edmund Reinhardt wrote:
I really appreciate this example. I have forwarded it to the debugger
developer and he said:
"Happy to help but currently working on a critsit at the moment and other
PMRs waiting on the queue. Either this should be raised as a PMR, if that's
not possible we can at least raise a defect. That way it won't get lost in
my inbox. What would you rather do? "
Sorry Edmund - I wasn't intending to report this /here/ as a defect. I
was hoping to get some consensus on whether other RDi people are
experiencing the same thing, preparatory to...
I am getting an internal defect opened but it will get more priority if it
comes from one of you guys.
...opening an official PMR. Which I shall do tomorrow after I clear my
desk a bit :-)
--buck
midrange.com
