[Bug] F10 key lets sockets sleep (?)

> Hi VM and Windows gurus,
> I have a strange problem for which I cannot find a work around. This is
> with Windows XP and VW 7.7.1 (although I had this problem with older
> versions as well - at least from VW 7.5, I guess).
> I have a Dialog with Buttons for the function key F2 to F11 (mimicking a
> Bloomberg Keyboard) which can get triggered by the mouse or the
> appropriate function key.
> The function is to append the appropriate string to the contents of an
> input field (f.ex. 'IBM US' then #F8 results in 'IBM US Equity') and
> send a request off to Bloomberg via a C interface (used to be COM with
> the same behavior).
> The strange thing is that #F10 does not work (F10 stands for Index which
> is used often). The key is recognized and the request is send off, but
> then the program hangs waiting for the result. But when I click on the
> dialog window (or any other window) or press any key, the result get
> delivered. All other functions keys work as expected and using the mouse
> to activate the button works fine as well.
> My theory is that the F10 keypress lets the socket get stuck, so that is
> does not react to incoming data any more. As soon as some window event
> (even another F10 keypress does it) gets processed, the socket becomes
> activ again.
> I tried to send all kinds of messages using vm primitives to try to
> revive the vw (like #raise, #focusIn etc.), but had no success.
> Sorry for the longish description...
> The question is: is there some vm primitive I could call to kick the vm
> back to life (like sending some raw event to the windows machinery)? Or,
> better, is this problem known and somebody works on the vm to solve it?
> Unfortunately I cannot provide a simple test case...
> Thanks - I would appreciate any helpful idea,
> Christian
>
>
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

> This problem has been recently addressed in our development builds. If
> you have access to 7.8 builds, would you mind trying the latest VM and
> seeing if you can reproduce the problem?
>
> On 12/6/2010 7:37 AM, Christian Haider wrote:
>  > Hi VM and Windows gurus,
>  > I have a strange problem for which I cannot find a work around. This is
>  > with Windows XP and VW 7.7.1 (although I had this problem with older
>  > versions as well - at least from VW 7.5, I guess).
>  > I have a Dialog with Buttons for the function key F2 to F11 (mimicking a
>  > Bloomberg Keyboard) which can get triggered by the mouse or the
>  > appropriate function key.
>  > The function is to append the appropriate string to the contents of an
>  > input field (f.ex. 'IBM US' then #F8 results in 'IBM US Equity') and
>  > send a request off to Bloomberg via a C interface (used to be COM with
>  > the same behavior).
>  > The strange thing is that #F10 does not work (F10 stands for Index which
>  > is used often). The key is recognized and the request is send off, but
>  > then the program hangs waiting for the result. But when I click on the
>  > dialog window (or any other window) or press any key, the result get
>  > delivered. All other functions keys work as expected and using the mouse
>  > to activate the button works fine as well.
>  > My theory is that the F10 keypress lets the socket get stuck, so that is
>  > does not react to incoming data any more. As soon as some window event
>  > (even another F10 keypress does it) gets processed, the socket becomes
>  > activ again.
>  > I tried to send all kinds of messages using vm primitives to try to
>  > revive the vw (like #raise, #focusIn etc.), but had no success.
>  > Sorry for the longish description...
>  > The question is: is there some vm primitive I could call to kick the vm
>  > back to life (like sending some raw event to the windows machinery)? Or,
>  > better, is this problem known and somebody works on the vm to solve it?
>  > Unfortunately I cannot provide a simple test case...
>  > Thanks - I would appreciate any helpful idea,
>  > Christian

> a Windows related issue:
>
> the function keys F10 - F12 seem to be treated specifically by the OS.
> Adding a Transcript output to the event dispatcher and pressing F9, F10
> and F11 three times yields the following output (tested with VW 7.7.1
> and VW 7.8-nov10.2 running on Windows Vista):
>
> a KeyPressedEvent - #F9
> a KeyReleasedEvent - #F9
> a KeyPressedEvent - #F9
> a KeyReleasedEvent - #F9
> a KeyPressedEvent - #F9
> a KeyReleasedEvent - #F9
> a KeyPressedEvent - #F10
> a KeyReleasedEvent - #F10
> a KeyReleasedEvent - #F10
> a KeyPressedEvent - #F10
> a KeyReleasedEvent - #F10
>
> so some events are missing.
>
> when clicking with the mouse after pressing a key, all key press/release
> events are logged:
>
> a KeyPressedEvent - #F9
> a KeyReleasedEvent - #F9
> a KeyPressedEvent - #F9
> a KeyReleasedEvent - #F9
> a KeyPressedEvent - #F9
> a KeyReleasedEvent - #F9
> a KeyPressedEvent - #F10
> a KeyReleasedEvent - #F10
> a KeyPressedEvent - #F10
> a KeyReleasedEvent - #F10
> a KeyPressedEvent - #F10
> a KeyReleasedEvent - #F10
> a KeyPressedEvent - #F11
> a KeyReleasedEvent - #F11
> a KeyPressedEvent - #F11
> a KeyReleasedEvent - #F11
> a KeyPressedEvent - #F11
> a KeyReleasedEvent - #F11
>
> on Linux, the function keys F10 - F12 are not treated specifically and
> work as expected.
>
> Am 07.12.2010 01:57, schrieb Andres Valloud:
>> This problem has been recently addressed in our development builds. If
>> you have access to 7.8 builds, would you mind trying the latest VM and
>> seeing if you can reproduce the problem?
>>
>> On 12/6/2010 7:37 AM, Christian Haider wrote:
>>   >  Hi VM and Windows gurus,
>>   >  I have a strange problem for which I cannot find a work around. This is
>>   >  with Windows XP and VW 7.7.1 (although I had this problem with older
>>   >  versions as well - at least from VW 7.5, I guess).
>>   >  I have a Dialog with Buttons for the function key F2 to F11 (mimicking a
>>   >  Bloomberg Keyboard) which can get triggered by the mouse or the
>>   >  appropriate function key.
>>   >  The function is to append the appropriate string to the contents of an
>>   >  input field (f.ex. 'IBM US' then #F8 results in 'IBM US Equity') and
>>   >  send a request off to Bloomberg via a C interface (used to be COM with
>>   >  the same behavior).
>>   >  The strange thing is that #F10 does not work (F10 stands for Index which
>>   >  is used often). The key is recognized and the request is send off, but
>>   >  then the program hangs waiting for the result. But when I click on the
>>   >  dialog window (or any other window) or press any key, the result get
>>   >  delivered. All other functions keys work as expected and using the mouse
>>   >  to activate the button works fine as well.
>>   >  My theory is that the F10 keypress lets the socket get stuck, so that is
>>   >  does not react to incoming data any more. As soon as some window event
>>   >  (even another F10 keypress does it) gets processed, the socket becomes
>>   >  activ again.
>>   >  I tried to send all kinds of messages using vm primitives to try to
>>   >  revive the vw (like #raise, #focusIn etc.), but had no success.
>>   >  Sorry for the longish description...
>>   >  The question is: is there some vm primitive I could call to kick the vm
>>   >  back to life (like sending some raw event to the windows machinery)? Or,
>>   >  better, is this problem known and somebody works on the vm to solve it?
>>   >  Unfortunately I cannot provide a simple test case...
>>   >  Thanks - I would appreciate any helpful idea,
>>   >  Christian
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>