[jira] [Closed] (GUACAMOLE-1999) Only one left click is selecting the character/empty space under cursor

["Hugaleno Bezerra (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hugaleno Bezerra closed GUACAMOLE-1999.
---------------------------------------
    Resolution: Invalid

We have discovered how to reproduce and fixed the problem. There were nothing wrong with the patch. Sorry for the mistake.

I'm closing this issue.

> Only one left click is selecting the character/empty space under cursor
> -----------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1999
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1999
>             Project: Guacamole
>          Issue Type: Bug
>          Components: Terminal
>    Affects Versions: 1.6.0
>            Reporter: Hugaleno Bezerra
>            Priority: Minor
>         Attachments: bug-select-1.gif, bug-select-2.gif, bug-select-3.gif, guac-bug.gif
>
>
> Sometimes the terminal start acting strange and only one click is enough to select the text/empty space under cursor. It occurs ramdomly, maybe is something with double/triple click logic  that in some occasion are not handling the mouse state correctly.
> The mouse is not being dragged, its just the click.
> Attached a gif to help understand the problem
>  
> Got more informations about it. I have attached new gifs to help find the root cause. 
>  
> The *bug-select-1.gif* shows that when I do one click(whithout dragging it) it selects the 0 number, double click selects 0.0 and the triple click select only the part to the left of the cursor and not the entire line
>  
> The *bug-select-2.gif* shows the same but selecting a number. The behavior is the same.
>  
> When selecting an empty space as showed in {*}bug-select-3.gif{*}, we get the same behavior.
>  
> I thinks that's more clear now that something related to double/triple click logic is causing this problem. I never seen such behavior prior 1.6.0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)