Hi Maxim, Thanks for the message, is this a known problem with other people, or am I the only one experiencing it? I've been doing some tests modifying the source file but so far I haven't been able to figure out what causes the problem or get any debug data to display in my browser.
I have included the flash.external.ExternalInterface library in the screenSharingDialog.lzx file and added this line to the keydown and keyup event handlers: ExternalInterface.call( "console.log" , k); But I'm not getting anything to display in Firebug. Is there a good way I can collect debug data from the Flash application? That would help me diagnose the problem. I've tried console-logging the Java application that is run by the person sharing their screen, but it doesn't indicate anything abnormal when the remote user presses spacebar, so I think the problem is with the Flash part of the application. Thanks, Andrew On 08/02/2012 10:17 PM, Maxim Solodovnik wrote: > Thanks for your investigation, I'll try to handle this (if will have > enough time) > Or you can propose the patch :) > > On Fri, Aug 3, 2012 at 12:03 PM, Andrew Sengul <and...@contrastco.com > <mailto:and...@contrastco.com>> wrote: > > Hi everyone, > > I posted about this a while ago and have since found some more about > input handling with the OpenMeetings remote control. Basically, my > problem is that when a user is remotely controlling another user's > screen through OpenMeetings, if the remote-controlling user presses the > spacebar or enter key, keyboard input to the remote screen stops > working. The mouse will still work, but no keys pressed will register on > the other user's computer. > > It looks like screen remote control within the Flash application is > handled by the OpenLaszlo file > singlewebapp/WebContent/swf10/screensharing/screenSharingDialog.lzx, and > there are a number of rules to address discrepancies in keycodes between > systems, but there appear to be no specific rules in that file governing > the spacebar or enter key. I can see that events fire when a key is > pressed (keydown) and released (keyup), so my guess at what's going > wrong is that there's something about the keyup event that causes it to > react badly to the use of the space and enter keys so that it shuts down > the keycode processing system entirely. Does anyone who's familiar with > the screenSharingDialog.lzx file know what could be happening? > > Also, has anyone else had problems with the spacebar and enter key > stopping keyboard input while remote-controlling another user's screen? > If something on my system is causing this, I'd really like to know what > it is. Any help is appreciated, thanks, > > Andrew > > > > > -- > WBR > Maxim aka solomax
