On Mon, Feb 6, 2017 at 9:14 PM, Hilaire <hilaire@drgeo.eu> wrote:

Thanks for the updated message.

Le 06/02/2017 �� 19:39, Sven Van Caekenberghe a ��crit :
> That last one is not correct. It has nothing to do with specific iteration selectors. It means: stop when execution returns in one of the argument blocks. It also works for #on:error: #streamContents: or any other message that accepts blocks as argument - which is pretty cool.

Strangely step over does not step in the bloc with #do: but does with
#to:do:

In the later case step over and through behave mostly the same, the
stack looks a bit different though.

Another question, I try to locate where the tooltips are set in the
debugger. I can't find it with traditional browser tools (send, class
use) and the finder:

The finder tells me "Through" is used in SpecThroughDebugAction, but
browser tells me there is no use case of this class. I see some pragma
in class side method, did it...
actionType
�� <debuggingAction>
�� <contextMenuDebuggingAction>

No user of actionType, but I guess user or pragma, how do you guys track
the logic from here

Seems that the logic for changing the tooltips is not that straightforward.

If you ping me once you decided for a the text of the tooltip I can add them.

If you want to look at it yourself here are some details:

Each action in the debugger is modeled as a subclass of��DebugAction.

The Glamour interface of the debugger uses DebugAction>>#asGlamourAction��

to transform that into a Glamour action. This action is then rendered in��GLMMorphicActionRenderer>>#render:.

There the tooltip is set directly by concatenating the title and the shortcut of the action.

Best solution would be to add a description attribute to DebugAction and GLMAction and then

modify GLMMorphicActionRenderer>>#render: to use it.

For the Spec interface of the debugger you need to adapt DebugAction>>#asMenuRegistrationIn:

Cheers,

Andrei

��

--
Dr. Geo
http://drgeo.eu