Smalltalk › Pharo › Pharo Smalltalk Developers

double selection in the debugger is confusing

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

stepharo

double selection in the debugger is confusing

Hi guy

we should disable the double selection when we click on a stack element
because we get selection in frame and in fill and this is confusing
because the PC is represented by the filled
one.

Stef

Screen Shot 2016-02-21 at 19.03.14.png (136K) Download Attachment

stepharo

Re: double selection in the debugger is confusing

Here this is terribly confusing because we could think that the
execution will go inside
the true block but no in reality it is jumping right after.
So we must remove this selection of matching terms.

Stef

Le 21/2/16 19:04, stepharo a écrit :
> Hi guy
>
> we should disable the double selection when we click on a stack element
> because we get selection in frame and in fill and this is confusing
> because the PC is represented by the filled
> one.
>
> Stef

Nicolai Hess-3-2

Re: double selection in the debugger is confusing

2016-02-21 19:19 GMT+01:00 stepharo <[hidden email]>:

Here this is terribly confusing because we could think that the execution will go inside
the true block but no in reality it is jumping right after.
So we must remove this selection of matching terms.

This was always like that, but with rubric, the "second selection" highlight is much more visible.

In older non-rubric text handling, the second selection was just a pale light color, without border.

Maybe we should remove the border for rubrics "second selection" text highlight.

Stef

Le 21/2/16 19:04, stepharo a écrit :

Hi guy

we should disable the double selection when we click on a stack element
because we get selection in frame and in fill and this is confusing because the PC is represented by the filled
one.

Stef

stepharo

Re: double selection in the debugger is confusing

Le 22/2/16 09:50, Nicolai Hess a écrit :

2016-02-21 19:19 GMT+01:00 stepharo <[hidden email]>:

Here this is terribly confusing because we could think that the execution will go inside
the true block but no in reality it is jumping right after.
So we must remove this selection of matching terms.

This was always like that, but with rubric, the "second selection" highlight is much more visible.

In older non-rubric text handling, the second selection was just a pale light color, without border.

Maybe we should remove the border for rubrics "second selection" text highlight.

Yes!

Stef

Le 21/2/16 19:04, stepharo a écrit :

Hi guy

we should disable the double selection when we click on a stack element
because we get selection in frame and in fill and this is confusing because the PC is represented by the filled
one.

Stef

Nicolai Hess-3-2

Re: double selection in the debugger is confusing

2016-02-23 8:46 GMT+01:00 stepharo <[hidden email]>:

Le 22/2/16 09:50, Nicolai Hess a écrit :

2016-02-21 19:19 GMT+01:00 stepharo <[hidden email]>:

Here this is terribly confusing because we could think that the execution will go inside
the true block but no in reality it is jumping right after.
So we must remove this selection of matching terms.

This was always like that, but with rubric, the "second selection" highlight is much more visible.

In older non-rubric text handling, the second selection was just a pale light color, without border.

Maybe we should remove the border for rubrics "second selection" text highlight.

Yes!

Ok, I'll open an issue entry and provide a fix. And you can discuss with Esteban if we want to include this

in the code freeze :-)

Stef

Le 21/2/16 19:04, stepharo a écrit :

Hi guy

we should disable the double selection when we click on a stack element
because we get selection in frame and in fill and this is confusing because the PC is represented by the filled
one.

Stef

EstebanLM

Re: double selection in the debugger is confusing

On 23 Feb 2016, at 08:49, Nicolai Hess <[hidden email]> wrote:

2016-02-23 8:46 GMT+01:00 stepharo <[hidden email]>:

Le 22/2/16 09:50, Nicolai Hess a écrit :

2016-02-21 19:19 GMT+01:00 stepharo <[hidden email]>:
Here this is terribly confusing because we could think that the execution will go inside
the true block but no in reality it is jumping right after.
So we must remove this selection of matching terms.

This was always like that, but with rubric, the "second selection" highlight is much more visible.
In older non-rubric text handling, the second selection was just a pale light color, without border.

Maybe we should remove the border for rubrics "second selection" text highlight.

Yes!

Ok, I'll open an issue entry and provide a fix. And you can discuss with Esteban if we want to include this
in the code freeze :-)

for me this is a bug, not an enhancement (is super annoying, and then an usability bug).

so I vote yes.

Stef

Le 21/2/16 19:04, stepharo a écrit :

Hi guy

we should disable the double selection when we click on a stack element
because we get selection in frame and in fill and this is confusing because the PC is represented by the filled
one.

Stef