Studio 8.1.4 not always stopping at breakpoints
Hi all,
It turns out this was due to an old library preference – $v3events –
which had come down through the versions since Omnis 7. For some reason
now forgotten in the mists of time, my Devops library had $v3events set
true.
Fortuitously the BugReport library was built by modifying a previous
library which had similarly come down through the ages. These were my
only 2 current libraries that had $v3events true. I shudder to think of
how much time I would have wasted if I had started by hacking a
BugReport library that had its $v3events false. As it was, I had one of
those “I totally rock as a developer” experiences because I was able to
reproduce the problem on the first try!
For people who downloaded my library from GitHub and replicated the bug
– thank you but don’t worry, it is a library preference affecting that
library only.
Thanks to UK support for the quick resolution. They said by default
$v3events would be turned off during library conversion from O7 to
Studio. So it follows that the other listers who have been experiencing
this problem in real life probably have libraries that were converted
from Omnis 7, and probably explicitly set $v3events true (and probably
don’t remember why!).
Plus, this got me to set up in GitHub so all in all not a bad day
yesterday. Even if my “I totally rock” experience did turn out to be
illusory. It was good while it lasted!
Cheers,
Reg
On 14/3/18 9:40 am, H.P. Noppe wrote:
> Hej Reg,
>
> In which situations does this occur? I did not run into this problem yet.
>
> Grtz Henk
>
>> On 13 Mar 2018, at 00:32, Reg Paling <reg.paling@lokanet.com> wrote:
>>
>> Hi all,
>>
>> I find that in Studio 8.1.4 development, it doesn’t always stop when it hits a breakpoint. This happens for hard-coded Breakpoint commands and also when hitting the breakpoint key combination. It probably also happens for “red dot” ide breakpoints.
>>
>> I’ve had quite a few occurrences of this now. At first I couldn’t pin it down – was it something I did, just something about my code, or a local corruption in one of my libraries? But now it has happened enough I’m confident that it’s real.
>>
>> Anyone else seeing this?
>>
>> Regards,
>> Reg
>>
>> _____________________________________________________________
>> Manage your list subscriptions at lists.omnis-dev.com
>> Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com