Hi, I'm having a problem with the EOS OLE on my laptop (both with version 1.2.0 & 1.2.1): if I press any button on the Virtual Keyboard the Windows User Interface 'freezes', i.e. no response to user input to EOS or any other application. Windows only starts responding again after one or two Ctrl-Esc sequences. e.g.
- Start EOS Offline
- Select Offline option from EOS shell
- Select Virtual Keyboard from Virtual Control list in Browser
- Click 'Cue' button (for example)
- => Cue button highlights in blue. Nothing else happens. No other buttons can be pressed. Alt-Tab switching doesn't work - essentially all user input is frozen. Any dynamic information already displayed on the screen, e.g. clock, timers on Diagnostic screen, continue to update in real-time.
Ctrl-Esc causes the Windows taskbar and Start Menu to be display over the top of EOS; sometimes I can then switch back to EOS and 'Cue' is then on the command line. Sometimes the Start Menu option and taskbar icons are frozen after the first Ctrl-Esc and only come back to life after the 2nd Ctrl-Esc. In this case a second 'Cue' is added to the command line and a syntax error is displayed. Hitting Backspace to clear the duplicate command causes another freeze...
If I have the Diagnostics window open on the top half of the screen before using the Virtual Keyboard, the loop times etc. keep cycling at their normal rate whilst the UI is frozen, but the Last Command doesn't update to 'Cue'. The overall CPU usage remains around 20%. I don't have the same problem on my desktop machine, so it does seem to be a EOS-Windows issue related to my laptop, but any ideas how to resolve it? Or information to collect and forward to support? My laptop is a 6-month old Sony Vaio (VGN-BX297XP) running Windows XP Pro. EOS is the the only application I've encountered this problem with. Also most other EOS screens with virtual buttons don't have this problem; apart from Virtual Sliders.
I'm in Toronto for a while so I am reliant on using my laptop for OLE work, and don't have immediate access to UK support. However on the positive side it does seem like the keyboard shortcuts are working OK for me, and therefore I should be able to avoid using the Virtual Keyboard at all, so this probably won't be a major issue. It would be good to understand what the problem is though.
