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
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
2016-02-21 19:19 GMT+01:00 stepharo <stepharo@free.fr>:
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
Le 22/2/16 09:50, Nicolai Hess a écrit :
2016-02-21 19:19 GMT+01:00 stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>:
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
2016-02-23 8:46 GMT+01:00 stepharo <stepharo@free.fr>:
Le 22/2/16 09:50, Nicolai Hess a écrit :
2016-02-21 19:19 GMT+01:00 stepharo <stepharo@free.fr>:
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
On 23 Feb 2016, at 08:49, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-02-23 8:46 GMT+01:00 stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>:
Le 22/2/16 09:50, Nicolai Hess a écrit :
2016-02-21 19:19 GMT+01:00 stepharo <stepharo@free.fr <mailto:stepharo@free.fr>>: 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
participants (3)
-
Esteban Lorenzano -
Nicolai Hess -
stepharo