Well, I'm trying to get parameter prompting working in Guacamole and am running into an issue that I'm having a very hard time figuring out. I've got prompting to the point where, when you click on the connection, it grabs the parameters that need to be prompted and displays a dialog in the middle of the screen with the names of the parameters and the appropriate field (text, number, password) for each parameter.
The issue I'm hitting is that when the prompt box is displayed I cannot type anything in the text boxes. They're there, the cursor blinks in them, but when I press keys on the keyboard nothing gets put into the box. To add to the strangeness, at this point I can press Ctrl-Shift-Alt and the hidden menu pops out (since the route has already changed to the client), and when the menu is displayed I can then click in the prompt boxes and type text into them. As soon as I press Ctrl-Shift-Alt, again, I lose the ability to type (although what I have typed, already remains). Also, whether the menu is displayed or not I can cut/copy/paste text into the prompt boxes, so it seems to be limited to actual typing on the keyboard that is problematic. I suspect that's what's happening is that the keydown/keypress/keyup events are being captured and sent to the not-quite-yet-active client connection rather than to the prompt dialog, and that I somehow need to stop that interception and allow the browser to handle the key events instead of passing them through. But I'm having trouble figuring out if that's really what's happening, and, if so, how to stop it. My current implementation has guacPrompt as a directive, with a controller within that, and a Prompt type implemented. It's very similar to the guacNotification/Notification code, but built to handle displaying text fields and without the timeout/progress display. Thanks, Nick
