I have been experiencing an aggravating thing for the past several Matlab releases and for which I am looking for troubleshooting advice. Unfortunately, I haven’t been able to identify a minimal example to reproduce it.
Sometimes, though, when I am stopped in debug mode within the workspace of some class method, if I hover the mouse over an object (of that class or perhaps also other classes), I am immediately catapulted to a breakpoint in the workspace of one of its set.property() methods. This new breakpoint was not set by me and no error messages are shown in the command window to indicate that it was raised by an error
As an example, the screenshot below shows an instance where I have stopped in a method called vmi() of class SegmentedLabelMap, whose parent class is MatDecomp.

When I then hover the mouse over "obj" as yellow-highlighted in the screenshot, the debugger transports me (see 2nd screenshot below) to a different location in the workspace of MatDecomp.get.meta(), which contains the definition of one of obj’s property get() methods. Moreover, a string of "datatipinfo" function calls now appears in the call stack, as yellow-highlighted in the 2nd screenshot.
I assume this occurs because the get.property() needs to be called to gather data for the datatip display. However, I wonder why it creates another breakpoint in get.meta() rather than just executing this to completion? In any case, I don’t like this behavior. Is there an Editor preference setting to turn it off?I have been experiencing an aggravating thing for the past several Matlab releases and for which I am looking for troubleshooting advice. Unfortunately, I haven’t been able to identify a minimal example to reproduce it.
Sometimes, though, when I am stopped in debug mode within the workspace of some class method, if I hover the mouse over an object (of that class or perhaps also other classes), I am immediately catapulted to a breakpoint in the workspace of one of its set.property() methods. This new breakpoint was not set by me and no error messages are shown in the command window to indicate that it was raised by an error
As an example, the screenshot below shows an instance where I have stopped in a method called vmi() of class SegmentedLabelMap, whose parent class is MatDecomp.

When I then hover the mouse over "obj" as yellow-highlighted in the screenshot, the debugger transports me (see 2nd screenshot below) to a different location in the workspace of MatDecomp.get.meta(), which contains the definition of one of obj’s property get() methods. Moreover, a string of "datatipinfo" function calls now appears in the call stack, as yellow-highlighted in the 2nd screenshot.
I assume this occurs because the get.property() needs to be called to gather data for the datatip display. However, I wonder why it creates another breakpoint in get.meta() rather than just executing this to completion? In any case, I don’t like this behavior. Is there an Editor preference setting to turn it off? I have been experiencing an aggravating thing for the past several Matlab releases and for which I am looking for troubleshooting advice. Unfortunately, I haven’t been able to identify a minimal example to reproduce it.
Sometimes, though, when I am stopped in debug mode within the workspace of some class method, if I hover the mouse over an object (of that class or perhaps also other classes), I am immediately catapulted to a breakpoint in the workspace of one of its set.property() methods. This new breakpoint was not set by me and no error messages are shown in the command window to indicate that it was raised by an error
As an example, the screenshot below shows an instance where I have stopped in a method called vmi() of class SegmentedLabelMap, whose parent class is MatDecomp.

When I then hover the mouse over "obj" as yellow-highlighted in the screenshot, the debugger transports me (see 2nd screenshot below) to a different location in the workspace of MatDecomp.get.meta(), which contains the definition of one of obj’s property get() methods. Moreover, a string of "datatipinfo" function calls now appears in the call stack, as yellow-highlighted in the 2nd screenshot.
I assume this occurs because the get.property() needs to be called to gather data for the datatip display. However, I wonder why it creates another breakpoint in get.meta() rather than just executing this to completion? In any case, I don’t like this behavior. Is there an Editor preference setting to turn it off? oop, matlab editor, display, datatipinfo, get.property, debugging MATLAB Answers — New Questions

​