cursor not moving to bottom of pickxyz output in Message window

[sfregosi]

Hi All,

I have this bug that I've been trying to investigate/fix but without luck. I'm not sure if this is just a me issue or others have encountered it. I can replicate it on my laptop and on a virtual machine that I remotely work on, but it doesn't always happen on my laptop. I am running Matlab 2020b and this occurs with the latest master branch.

My workflow is a open Triton, open an LTSA, toggle on the Pickxyz button so I can keep a scratchpad of start/end times to investigate further, and then click either in the LTSA or in a spectrogram view and I get the following error message in the Command Window:

Error using eval
Check for missing argument or incorrect argument data type in call to function 'getComponent'.
Error in disp_pick (line 15)
eval('jDisp = jDEdit.getComponent(0).getComponent(0);')
Error in pickxyz (line 107)
            disp_pick([str,' ', info_struct.plot]); 
Error while evaluating Figure WindowButtonDownFcn.

Working my way back to try to debug, I found that line 14 in disp_pick, line 14 results in jDEdit being a 1x0 handle, which causes line 15 to throw the error. Stepping in from there, findobj seems to do ok until line 268 when it process the 'position' argument, I end up with an empty foundIdx variable and that breaks things moving forward. I'm not familiar enough with Matlab figure handles and GUIs to get any further than this.

Last week when this issue was not happening on my laptop but was happening on the virtual machine, I did a step-by-step walk through in parallel (thinking the issue was just the virtual machine). In that case, when it was working correctly, line 14 in disp_pick was not returning an empty handle and all proceeded without error. But, coming back to it this week, I'm now getting the same error on my laptop.

This isn't a critical bug, its just annoying as it dings every time and I can't see the output of later picks because they are lost down low in the message window (can scroll to them but each subsequent pick resets to the top). But, if anyone else has encountered this or wants to try to work together to fix it, I'd be happy to do that!! Thanks, Selene