Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-21 Thread Marcus Denker
> On 21 Jun 2016, at 16:48, stepharo wrote: > > marcus > > do you expect to have object centric debugging features in the near future? > Yes, we have already support for it using conditions on meta links… I want to use that first and later look into optimising (so the

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-21 Thread stepharo
marcus do you expect to have object centric debugging features in the near future? Stef Le 21/6/16 à 11:19, Marcus Denker a écrit : Hi, Another small iteration: now you can mouse over the Icon of #halOnce and #haltOnCount: and the current state is displayed (if the haltOnce is active, the

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-21 Thread Tudor Girba
Awesome! Doru > On Jun 21, 2016, at 11:19 AM, Marcus Denker wrote: > > Hi, > > Another small iteration: now you can mouse over the Icon of #halOnce and > #haltOnCount: and the > current state is displayed (if the haltOnce is active, the count of the >

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-21 Thread Marcus Denker
Hi, Another small iteration: now you can mouse over the Icon of #halOnce and #haltOnCount: and the current state is displayed (if the haltOnce is active, the count of the #haltOnCount:). this is in 60 update 101 Marcus

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-18 Thread Eliot Miranda
On Sat, Jun 18, 2016 at 12:17 AM, Marcus Denker wrote: > > On 18 Jun 2016, at 06:55, Marcus Denker wrote: > > > On 18 Jun 2016, at 05:29, Eliot Miranda wrote: > > Marcus, > > >> Marcus >> > > Yes, but using the

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-18 Thread Marcus Denker
> On 18 Jun 2016, at 06:55, Marcus Denker wrote: > > >> On 18 Jun 2016, at 05:29, Eliot Miranda > > wrote: >> >> Marcus, >> >> >> Marcus >> >> Yes, but using the byte code pc is a much much cheaper

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-17 Thread Marcus Denker
> On 14 Jun 2016, at 09:47, marcus.den...@inria.fr wrote: > > Hi, > > Yesterday we improved #haltOnce to be more like a “once” BreakPoint: > > -> state per *each* haltOnce send > (this means you can put two in one method and they are > independent) > -> when putting

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-14 Thread Tudor Girba
Wow! I particularly love how straightforward it is to distinguish between two haltOnce. Amazing work. Cheers, Doru > On Jun 14, 2016, at 9:47 AM, marcus.den...@inria.fr wrote: > > Hi, > > Yesterday we improved #haltOnce to be more like a “once” BreakPoint: > > -> state per *each*

[Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-14 Thread marcus . denker
Hi, Yesterday we improved #haltOnce to be more like a “once” BreakPoint: -> state per *each* haltOnce send (this means you can put two in one method and they are independent) -> when putting a haltOnce, it is enabled by default -> The global menu entry