On Wed, Feb 8, 2017 at 8:24 PM, Hilaire wrote:
> Here my proposals. Please propose better alternative.
>
> Le 07/02/2017 à 21:02, Hilaire a écrit :
> > Full stack
>
> I really don't know what to write there.
>
Show the complete stack. By default the stacks shows a limited number of
stack frames.
Here my proposals. Please propose better alternative.
Le 07/02/2017 à 21:02, Hilaire a écrit :
> Full stack
I really don't know what to write there.
>
> Run to here
Execute methods up to the text cursor position and return debugger control.
> Where is?
Show the next method to be executed (s
looks good to me.
On Tue, Feb 7, 2017 at 8:40 AM, Sven Van Caekenberghe wrote:
>
> > On 7 Feb 2017, at 08:05, Stephane Ducasse
> wrote:
> >
> > Sven I do not get
> >
> > Step over the highlighted message, i.e. do not follow the sent message,
> taking debugger control after the method invoked re
As we are here, what are your best proposals for these buttons:
Full stack
Run to here
Where is?
Le 06/02/2017 à 21:25, Sean P. DeNigris a écrit :
> How about...
--
Dr. Geo
http://drgeo.eu
ok got it!
Le 07/02/2017 à 20:49, Andrei Chis a écrit :
> Seems that I made a small mistake before.
> DebugAction>>#asMenuRegistrationIn: is called only when creating the
> context menu.
> SpecDebuggerDynamicToolbar is the class that builds the toolbar with the
> step buttons. Then each button wi
Seems that I made a small mistake before.
DebugAction>>#asMenuRegistrationIn: is called only when creating the
context menu.
SpecDebuggerDynamicToolbar is the class that builds the toolbar with the
step buttons. Then each button will be an instance of SpecDebugActionButton.
Andrei
On Tue, Feb 7,
Changed to the SpecDebugger in the method mentionned bellow does not
have action on newly debuggin session with SpecDebugger. This method is
not call. Any idea?
Le 06/02/2017 à 21:57, Andrei Chis a écrit :
> For the Spec interface of the debugger you need to adapt
> DebugAction>>#asMenuRegistratio
Ok thanks for the tips.
As labes was use as tooltip too I have to set the balloon text as bellow
which is not great but should help for the transition.
setBalloonText: ((anAction help ifNil: [ anAction title]) , Character
tab asString , anAction shortcutAsString) trimBoth;
I will look at the tip
Hi Hilaire,
I find your use case interesting. It used to be the case, that one could
discover an application commands by exploring the objects making up the
GUI...
Now, with Spec or Glamour, is that still the case? It seems not any more.
Doru, can you confirm?
Regards,
Thierry
2017-02-06 21:48
> On 7 Feb 2017, at 08:05, Stephane Ducasse wrote:
>
> Sven I do not get
>
> Step over the highlighted message, i.e. do not follow the sent message,
> taking debugger control after the method invoked returns or whenever
> execution should return inside a block used as an argument before that
Sven I do not get
Step over the highlighted message, i.e. do not follow the sent message,
taking debugger control after the method invoked returns or whenever
execution should return inside a block used as an argument before that.
in particular the taking debugger control
may be
give back debugg
> On 6 Feb 2017, at 21:25, Sean P. DeNigris wrote:
>
> How about...
>
> Into
>
> Step into the highlighted message, i.e. dive the debugger into the method
> which handles it
>
> Over
>
> Step over the highlighted message, i.e. execute it, but keep the debugger
> focused on the current method
On Mon, Feb 6, 2017 at 9:14 PM, Hilaire 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 bl
Ok, give a look to SpecDebugActionButton, this class has no user, only
progma reference, not easy to track the logic.
Never mind I test on a halt in its #update method. Nothing happen when
opening the debugger. May be there is instance in memory, no idea under
which name it is referenced, may be n
How about...
Into
Step into the highlighted message, i.e. dive the debugger into the method
which handles it
Over
Step over the highlighted message, i.e. execute it, but keep the debugger
focused on the current method
Through
Like stepping "Over", except step through block contents when execu
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
> On 6 Feb 2017, at 18:55, Hilaire wrote:
>
> How will you describe these buttons in the debugger?
> Here are proposals for tooltips, please fix it, I am sure there are
> better way to write it.
>
> Proceed
> Quit the debugger and resume the execution of the method.
>
> Restart
> Reset the loc
How will you describe these buttons in the debugger?
Here are proposals for tooltips, please fix it, I am sure there are
better way to write it.
Proceed
Quit the debugger and resume the execution of the method.
Restart
Reset the local variable and restart stepping at the beginning of the
method.
18 matches
Mail list logo
