Hi Stef, The bug with Run to Here should be fixed. This and al the other actions should work just like in the current debugger. This means that when the current debugger breaks they would also break :)
There are still some issues with the ui when there is unsaved content in the editor but it is usable. Andrei On Thu, Jan 31, 2013 at 10:16 PM, Stéphane Ducasse < [email protected]> wrote: > > On Jan 31, 2013, at 1:35 PM, Andrei Vasile Chis wrote: > > > > > Hi Stef, > > > > Andrei I will integrate the Spec Widget Changes now. > > Then I played with the debugger with vanessa and we got a bit lost > because the text selection does not show > > where is the expression currently with over or into. > > > > This should be fixed now. > > > > > > At one point we got to new process and it blocked also everything. > > > > Not good. Do you what you deed? > > step into …. or something like that until I arrived to newProcess > > I can restart and retry because I'm a bug attractor. > > > > > > > So after restarting in a new image we tried run to here and we were > confused :) > > > > do: aBlock > > "Refer to the comment in Collection|do:." > > 1 to: self size do: > > [:index | aBlock value: (self at: index)] > > > > I put the cursor in the block before aBlock and clicked on Run to Here > but nothing happened > > > > I will look at this. In theory now it should work like in the current > debugger. > > > > Also now in the spec interface I get some very strange bugs that are not > in the glamour one. > > Somehow some things do not update ok. I'll dig to see what happens. > > > > I'll let you know when I have something more. > > > > Andrei > > > > >
