View Single Post
Old 02-26-2011, 02:35 PM   #6
rkomar
Wizard
rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.rkomar ought to be getting tired of karma fortunes by now.
 
Posts: 3,055
Karma: 18821071
Join Date: Oct 2010
Location: Sudbury, ON, Canada
Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633
Quote:
Originally Posted by J.C. View Post
well the bluetooth stack most likely can support this easily, how the device handles the input is another matter.
I'm sure this is the real problem in adding support for a bluetooth keyboard. It would have to seamlessly work through the software keyboard's interface, since that is how most applications currently get their character input. It sounds simple to implement, but the devil is in the details. The software keyboard is different in its behaviour from a real keyboard (it only appears when explicitly called, and goes away when you hit "enter", passing its data to a handler at that time). Software key presses are not real events like the device button presses are. Do you still show the software keyboard if there is a bluetooth one? If not, how do you echo the characters before "enter" is pressed and the data is sent to the handler?... I'm sure it is possible to get working, but I doubt it is trivial to do.

Last edited by rkomar; 02-28-2011 at 01:32 AM. Reason: Seemlessly -> seamlessly. Ugh.
rkomar is offline   Reply With Quote