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

Michael Jumper resolved GUACAMOLE-121.
--------------------------------------
    Resolution: Invalid

Closing as invalid, as this described behavior is simply the natural 
consequence of:

# Forcing Unicode events (which have different semantics)
# The browser preventing JavaScript from controlling all keyboard shortcuts 
(which is the browser's prerogative)

I've opened a new issue for adding a Swiss-French layout, which should address 
the underlying difficulty here: GUACAMOLE-135

If you'd like to help contribute that layout, please comment there or within 
the mailing lists. We'll help however we can.

> Ctrl/Alt key combinations not working
> -------------------------------------
>
>                 Key: GUACAMOLE-121
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-121
>             Project: Guacamole
>          Issue Type: Improvement
>    Affects Versions: 0.9.10-incubating
>            Reporter: J-M Roth
>
> If you are working fast (actually using the keyboard to more than type text 
> and not use the mouse to click all the time) you definitely need Ctrl/Alt+key 
> combinations to work.
> For example when searching something in the browser, you want to use Ctrl+F 
> for "find" (and not go and click around in the menu, how retro is that). The 
> same goes for Alt+key of course.
> I understand that the event will go to the local browser, and not to the 
> application inside Guacamole, however something should be done to improve 
> that (provide at least some keyboard combination that simulates the use of 
> those keys).
> Using the onscreen Ctrl/Alt key is not working BTW.
> (As a sidenote: can "Ctrl-W" be trapped, such that the guacamole window is 
> not closed when used? (Especially bad when you like to use a Linux terminal 
> inside Guac, and are used to using shortcuts like deleting works using 
> Ctrl+W) ^^)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to