On Wed, Sep 19, 2012 at 8:40 AM, Dave <[email protected]> wrote:
> I have been told that this maybe happening because “the real-time kernal > which gives absolute priority to the motor control thread is interrupting the > “fake keyboard” input of the bar code reader”. It's probably not that the kernel doesn't listen to the keyboard, but the timing of the control transfer to the file widget. The 'o' causes the widget to pop up, but it takes a little time, and the focus doesn't transfer to the file dialog right away. This also means that the first few characters of the filename still go to the command line and are interpreted as commands, which could maybe explain your mysterious jogs. There is no reliable solution to this: you can't control timing of the focus transfer. In normal usage, you press the command and start typing the filename when you get the visual cue of the window popping up. You could try a hack of including a generous amount of spaces or some other character that doesn't do anything important in both the interpreter and the file dialog (tabs?newlines?Ctrl-L?) between the 'o' and the filename. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
