I do not get your point. I do not see why this is mode.
If the cursor is already on something or at the end or beginning of
something clicking on the same place, select it.
This is just different but it works. and it is not incompatible with
also supporting double clicking. So why now we
cannot have the previous behavior which was compatible with what the
world is doing but in addition let us
work.
We can also say that double clicking is strange.
Hi,
I can see how people get use with this behavior, but I am quite
certain that the solution from PluggableTextMorph was a workaround
solution due to a missing double click event. Now we have that event
and we can use it where it is appropriate.
It's not that we copy things for the sake of copying, but I simply
think double clicking is a better choice here. click-pause-click
introduces, from a cognitive perspective, a hidden modal mode. That
is, you have no chance of knowing in which state you are. I was
several times annoyed by inadvertently selecting pieces of code (often
during demos). At the same time, I believe it is reasonable to assume
that programmers know how to double click.
So, yes, I did think of it quite explicitly :)
Doub
Cheers,
Doru
On Tue, Sep 30, 2014 at 10:46 PM, Nicolas Cellier
<[email protected]
<mailto:[email protected]>> wrote:
I find click pause click useful.
No stress nor necessary adjustment of double-click delay.
What could be the intention of a user clicking repeatedly on the
same area?
Did you think of it?
If copying what everyone else does is the sole value, then let's
not do Pharo.
2014-09-30 21:34 GMT+02:00 Tudor Girba <[email protected]
<mailto:[email protected]>>:
Hi,
I explained before but it went unnoticed. The selection
happens on double click like in any other editor.
The regular PluggableTextMorph also tries to do it on a kind
of a double click, only it is implemented as
click-pause-click. So, if you click once, wait 5 minutes, and
click again, it will select. This is not particularly useful.
So, Rubric selects on double click.
Now, as I mentioned before, there happens to be a random
double click issue. I cannot reproduce it, but sometimes it
happens. Also, when I save the image and load it back, the
problem is gone. Please note that this issue is not related to
Rubric, but to the double click event throughout the entire
image. For example, if you see that double click does not work
in Rubric, try to double click on the window title to maximize
a window and you will see that it does not work.
Cheers,
Doru
On Tue, Sep 30, 2014 at 8:42 PM, stepharo <[email protected]
<mailto:[email protected]>> wrote:
With the previous tools I can select a piece of text by
clicking after its last element and now I cannot
or I can but sometimes.
So what is the fix?
Stef
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
--
www.tudorgirba.com <http://www.tudorgirba.com>
"Every thing has its own flow"
