Smalltalk › Pharo › Pharo Smalltalk Developers

Did we lose edit-in-place in GT Inspector in Pharo 6?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Sean P. DeNigris

Did we lose edit-in-place in GT Inspector in Pharo 6?

Administrator

Double clicking on a value in the raw tab seems to have no effect.

p.s I asked twice in Discord with no response. I guess I'm finally getting old enough that I don't understand how to use new platforms ;)

Cheers,
Sean

Tudor Girba-2

Re: Did we lose edit-in-place in GT Inspector in Pharo 6?

Hi,

Indeed, this feature is temporarily not available due to the move to FastTable, but we are working on adding it back.

Doru

> On Mar 12, 2017, at 3:36 AM, Sean P. DeNigris <[hidden email]> wrote:
>
> Double clicking on a value in the raw tab seems to have no effect.
>
> p.s I asked twice in Discord with no response. I guess I'm finally getting
> old enough that I don't understand how to use new platforms ;)
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/Did-we-lose-edit-in-place-in-GT-Inspector-in-Pharo-6-tp4938264.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>

--
www.tudorgirba.com
www.feenk.com

"It's not how it is, it is how we see it."

Sean P. DeNigris

Re: Did we lose edit-in-place in GT Inspector in Pharo 6?

Administrator

Tudor Girba-2 wrote

this feature is temporarily not available due to the move to FastTable

Tudor Girba-2 wrote

but we are working on adding it back.

:)

I use this all the time to e.g. nil out an inst var to re-lazily-initialize. I noticed it was missing (after trying to press the mouse button harder for a few minutes... sigh) within minutes of testing out Pharo 6. There was no setter, so I ended up doing an ugly, and time-consumiung, `#instVarNamed:put:`. Will it be re-added in 6 before the release? I'd say a lost key feature is a bug, no?

Cheers,
Sean

Andrei Chis

Re: Did we lose edit-in-place in GT Inspector in Pharo 6?

On Sun, Mar 12, 2017 at 5:07 PM, Sean P. DeNigris <[hidden email]> wrote:

Tudor Girba-2 wrote
> this feature is temporarily not available due to the move to FastTable

:(

Tudor Girba-2 wrote
> but we are working on adding it back.

:)

I use this all the time to e.g. nil out an inst var to re-lazily-initialize.
I noticed it was missing (after trying to press the mouse button harder for
a few minutes... sigh) within minutes of testing out Pharo 6. There was no
setter, so I ended up doing an ugly, and time-consumiung,
`#instVarNamed:put:`. Will it be re-added in 6 before the release? I'd say a
lost key feature is a bug, no?

This feature was lost because of the inspector move to FastTable and the adding of automatic refresh.

But we hope to add it back for Pharo 6. Just it will be enabled on Shift+Click and not double click.

Cheers,

Andrei

-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Did-we-lose-edit-in-place-in-GT-Inspector-in-Pharo-6-tp4938264p4938297.html

Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

alistairgrant

Re: Did we lose edit-in-place in GT Inspector in Pharo 6?

In reply to this post by Sean P. DeNigris

On 12 March 2017 at 03:36, Sean P. DeNigris <[hidden email]> wrote:
> Double clicking on a value in the raw tab seems to have no effect.
>
> p.s I asked twice in Discord with no response. I guess I'm finally getting
> old enough that I don't understand how to use new platforms ;)

While I'm feeling much the same (about being old and not
understanding), and can empathise, I think in this case it is simply
that the chat platforms are in flux at the moment. Esteban has
requested we move to Discord, but the numbers are still fairly low.
Hopefully things will improve soon. I.e. don't give up on discord
just yet. :-)

Cheers,
Alistair