Difference between revisions of "Talk:Linden Lab Bounties"
m (minor wikification) |
|||
| Line 6: | Line 6: | ||
[[User:SignpostMarv Martin|SignpostMarv Martin]] 19:24, 8 January 2007 (PST) | [[User:SignpostMarv Martin|SignpostMarv Martin]] 19:24, 8 January 2007 (PST) | ||
== Keyboard Input == | |||
I have been thining briefly about the keyboard hack thing. | I have been thining briefly about the keyboard hack thing. | ||
Sounds to me like a classical case of having to implement a producer/consumer pattern. Have a set of platform dependent producers, possibly extendable via plugins, produce input events from, various devices, e.g. keyboard, mouse, etc. | Sounds to me like a classical case of having to implement a producer/consumer pattern. Have a set of platform dependent producers, possibly extendable via plugins, produce input events from, various devices, e.g. keyboard, mouse, etc. | ||
Revision as of 09:54, 13 January 2007
Category:Bounties
This article should be added to Category:Bounties at the nearest available opportunity, as should any future articles pertaining to individual bounties.
Don't forget to create Category:Linden Lab Bounties at the appropriate time either. SignpostMarv Martin 19:24, 8 January 2007 (PST)
Keyboard Input
I have been thining briefly about the keyboard hack thing. Sounds to me like a classical case of having to implement a producer/consumer pattern. Have a set of platform dependent producers, possibly extendable via plugins, produce input events from, various devices, e.g. keyboard, mouse, etc.
Abstract the input events, in such a fashion, that new input event types are possible.
Either create a new thread for driving the producers/consumers or drive the producers and consumers.
At the same time, tools and toolset should be refactored as input event consumers, the current way of having globals defined for tools does not appear to be sufficiently flexible for future needs. Duffy Langdon