Hi,
Indeed, this is a usability issue.
However, your code is not lost. You can find the playground easily, and if
you inspect the same objects, the raw presentation will show you the last
entered code for each class.
Cheers,
Doru
On Fri, May 29, 2015 at 6:15 PM, Esteban A. Maringolo <emaring...@gmail.com>
wrote:
> Also... I find myself accidentally closing the whole Playground in an
> attempt to just close the inspector.
>
> I know this is related with me not being the smartest guy in the
> block, but I'm so used to discard inspectors, and when you're somehow
> deep inspecting you completely forgot you started in a "workspace".
>
>
>
> Esteban A. Maringolo
>
>
> 2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <emaring...@gmail.com>:
> > 2015-05-29 12:36 GMT-03:00 Tudor Girba <tu...@tudorgirba.com>:
> >> Hi,
> >>
> >> Indeed, this part of the inspector will be revisited for Pharo 5.
> >
> > Good. I'm sure this can be backported easily ;)
> >
> >> But, what exactly do you mean by " I just want to select it to run an
> >> expression where self refers to the inspected object"?
> >
> > I have the strong habit of running expressions (it is, send messages)
> > to objects directly in the inspector, in the case of the example
> > array, I can fiddle selecting the different elements in the array and
> > finally select the array itself ("self") to select as the receiver. I
> > expect to write these expression on the pane of the right, even when I
> > could do it on the pane of the left.
> >
> > I hope I explained myself. :)
> >
> >
> > Esteban A. Maringolo
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
