> On 17 Jan 2016, at 16:52, Tudor Girba <tu...@tudorgirba.com> wrote:
> 
> Hi,
> 
>> On Jan 17, 2016, at 1:18 PM, David Allouche <da...@allouche.net> wrote:
>> 
>> Cool. While you are there, could provide a way to separate instance 
>> variables from local variables (and class shared variables too, maybe)?
>> It could be different columns, filtering, tabs, I do not really care. 
>> Currently, when debugging classes with lots of instance variables (like 
>> morphic stuff) it's quite painful to find the one local variable of 
>> interest. 
> 
> 
> The tags to the left of each variable can be used to filter the list of 
> variables.

Nice, but:

It's not an obvious, standard UI behaviour
In a complex class, you still need to hunt through the list to find the first 
local variable, that's frustrating.

You cannot even use incremental search there. That should probably be a 
wishlist item on the bug tracker.

> 
>> Also, could the scroll position in the variable be preserved while stepping?
> 
> I am not sure what you refer to. The currently selected variable is preserved 
> both when you step, and it is even preserved when you switch back and forth 
> through the stack.
> 
> What am I missing?

The selected variable is preserved, but if ones scroll the variable list using 
the mouse wheel, the scroll position changes but not the selection.

Stepping resets the scroll position to show the selected variable, which is 
"self" by default.

I would like the scroll position for the variable list to be remembered by the 
debugger in each object. Or maybe the right granularity is concrete class, I am 
not sure.

>> Unfortunately, Pharo does not appear to receive ctrl-tab keydown events, so 
>> I need to reach for the mouse to move the focus out of any text area…
> 
> Indeed, this does not work.

I already reported that before on the mailing list, and I have tracked it down 
to ctrl-tab keydown not even reaching Sensor. The corresponding keyup are 
correctly detected. So I guess it might be a vm issue.

I should probably file a proper bug report.

Reply via email to