Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #7128 > unrolled thread
| Started by | gyenchev@gmail.com |
|---|---|
| First post | 2014-07-27 23:39 -0700 |
| Last post | 2014-07-29 17:58 +0100 |
| Articles | 5 — 3 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
Multimedia keys not workin in VO apps. gyenchev@gmail.com - 2014-07-27 23:39 -0700
Re: Multimedia keys not workin in VO apps. Malcolm G <malcolm-news2012delete@delete.jobstream.com> - 2014-07-28 13:00 +0100
Re: Multimedia keys not workin in VO apps. gyenchev@gmail.com - 2014-07-29 03:29 -0700
Re: Multimedia keys not workin in VO apps. dlzc <dlzc1@cox.net> - 2014-07-29 07:22 -0700
Re: Multimedia keys not workin in VO apps. Malcolm G <malcolm-news2012delete@delete.jobstream.com> - 2014-07-29 17:58 +0100
| From | gyenchev@gmail.com |
|---|---|
| Date | 2014-07-27 23:39 -0700 |
| Subject | Multimedia keys not workin in VO apps. |
| Message-ID | <4fe52236-e432-4162-9486-d209da38bc7a@googlegroups.com> |
Has someone ecountered the problem where the multimedia keys on the keyboard (Volume Up,Volume Down, Play, Pause, etc.) are not working. The strange thing is that on some keyboards they work with no problem in VO apps, on some keyboards part of the keys work and on some all of them are not working. The problem can be reproduced on VO 2.7, 2.8. Has someone ecountered that problem and is there a workaround? Greetings, Georgi.
[toc] | [next] | [standalone]
| From | Malcolm G <malcolm-news2012delete@delete.jobstream.com> |
|---|---|
| Date | 2014-07-28 13:00 +0100 |
| Message-ID | <iXqBv.439379$Im4.304274@fx03.am4> |
| In reply to | #7128 |
On 28/07/2014 07:39, gyenchev@gmail.com wrote: > Has someone ecountered the problem where the multimedia keys on the keyboard (Volume Up,Volume Down, Play, Pause, etc.) are not working. > The strange thing is that on some keyboards they work with no problem in VO apps, on some keyboards part of the keys work and on some all of them are not working. > The problem can be reproduced on VO 2.7, 2.8. > Has someone ecountered that problem and is there a workaround? I have seen (and looked into) the problem using both VO and the VO GUI classes in Vulcan. So far I don't know why it goes wrong or how to work around it.
[toc] | [prev] | [next] | [standalone]
| From | gyenchev@gmail.com |
|---|---|
| Date | 2014-07-29 03:29 -0700 |
| Message-ID | <e7e4addd-44a6-41ec-86f0-32007d1c07f9@googlegroups.com> |
| In reply to | #7129 |
On Monday, July 28, 2014 3:00:14 PM UTC+3, Malcolm G wrote: > On 28/07/2014 07:39, gyenchev@gmail.com wrote: > > > Has someone ecountered the problem where the multimedia keys on the keyboard (Volume Up,Volume Down, Play, Pause, etc.) are not working. > > > The strange thing is that on some keyboards they work with no problem in VO apps, on some keyboards part of the keys work and on some all of them are not working. > > > The problem can be reproduced on VO 2.7, 2.8. > > > Has someone ecountered that problem and is there a workaround? > > > > I have seen (and looked into) the problem using both VO and the VO GUI > > classes in Vulcan. So far I don't know why it goes wrong or how to work > > around it. Thanks for the reply. If anyone has seen the problem and has a solution, or any suggestion at all please reply.
[toc] | [prev] | [next] | [standalone]
| From | dlzc <dlzc1@cox.net> |
|---|---|
| Date | 2014-07-29 07:22 -0700 |
| Message-ID | <47fe55d8-a310-4a24-9279-634f8a30a6c0@googlegroups.com> |
| In reply to | #7131 |
Dear gyen...: On Tuesday, July 29, 2014 3:29:33 AM UTC-7, gyen...@gmail.com wrote: ... > If anyone has seen the problem and has a > solution, or any suggestion at all please reply. This is pretty spottily reported in Micro$haft literature, for other programs. If the problem follows the keyboard, then it may be that the multimedia keys are implemented differently between them (some as impossible key configurations, and others in different ways). Alternatively, I would guess the keyboards that carry the problem might load their driver behind the VO application, so your application collects these "keystrokes" and doesn't know what to do with them... no real way to push them back into the Windoze buffer, and no guarantee you might not have an infinite loop putting them back in. Not really an answer to say "get a better keyboard"... but you might see if that is what happens... the problem follows the keyboard around. USB devices load their own drivers... David A. Smith
[toc] | [prev] | [next] | [standalone]
| From | Malcolm G <malcolm-news2012delete@delete.jobstream.com> |
|---|---|
| Date | 2014-07-29 17:58 +0100 |
| Message-ID | <soQBv.306846$YB.227229@fx28.am4> |
| In reply to | #7132 |
On 29/07/2014 15:22, dlzc wrote: > Dear gyen...: > > On Tuesday, July 29, 2014 3:29:33 AM UTC-7, gyen...@gmail.com wrote: > ... >> If anyone has seen the problem and has a >> solution, or any suggestion at all please reply. > > This is pretty spottily reported in Micro$haft literature, for other programs. > > If the problem follows the keyboard, then it may be that the multimedia keys are implemented differently between them (some as impossible key configurations, and others in different ways). > > Alternatively, I would guess the keyboards that carry the problem might load their driver behind the VO application, so your application collects these "keystrokes" and doesn't know what to do with them... no real way to push them back into the Windoze buffer, and no guarantee you might not have an infinite loop putting them back in. > > Not really an answer to say "get a better keyboard"... but you might see if that is what happens... the problem follows the keyboard around. USB devices load their own drivers... Certainly the keyboard i was debugging was using the official microsoft back/forward/calculator/volume up/volume down keyboard messages
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web