Hi Stef, Thanks for your comments. In particular, the one about clicking on the current cursor. I never saw it like that because I always used the mouse. So in fact, I was wrong in seeing it as click-pause-click because it should have been as click-on-cursor. I actually like this one.
However, the current behavior from TextMorph is incompatible with double click because if I double click on the cursor, then the selection is set and then deleted because the current implementation treats the double click as two clicks. But, I believe we could change that one and have both the click-on-cursor and the double-click select. I opened a ticket: https://pharo.fogbugz.com/f/cases/14132/Rubric-should-support-click-on-cursor Cheers, Doru On Wed, Oct 1, 2014 at 7:51 AM, stepharo <[email protected]> wrote: > > My perception is that this kind of small changes adds no value. >> It just removes a small bit of value. >> So it's going to frustrate someone for nothing. >> Not a big frustration, I concede, but a gratuitous one. >> > > I think its the opposite. People will simply adapt. > > > Seriously I find that attitude really sad. > So why don't add TxText with average syntax higthlitghting and that igor > just does something else > on the sake that people will adapt. > > For me there is no justification for not having the same behavior with is > working perfectly well. > It is not a question of dogma but just pragmatic > - it works well > - it is handy > - it is not incompatible with the double click dogma. > > > > Finally, the best thing it brings is exposing that some events are >> handled incorrectly. >> At least I hope it will give us a chance to correct them :) >> > > :) > > Doru > > > >> >> 2014-09-30 22:59 GMT+02:00 Tudor Girba <[email protected]>: >> >>> 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]> 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]>: >>>> >>>>> 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]> 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 >>>>> >>>>> "Every thing has its own flow" >>>>> >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"
