Open GoogleCodeExporter opened 8 years ago
what keyboard layout did you set in BTstack Keyboard?
CTRL is not intended to produce visible characters. CTRL-H is TAB, CTRL-A let's
you go to the beginning of a line in terminal apps, etc. Try ALT for
alternative characters, but they are sparsely mapped. e.g. ALT-L is @ on a
German keyboard.
Original comment by matthias.ringwald@gmail.com
on 17 Aug 2010 at 6:44
Keyboard is set to English (US). I believe that the Shift key should also not
produce visibile characters yet it is being read and producing the accented "a"
and therefore Shift-a will show as accented a-regular a but not capitalized. I
had all the languages and none allowed the Shift to work properly... The
Hebrew, Serbian and Korean keyboards showed some native characters but the
other languages did not allow any special characters.
Original comment by jose...@dollarphone.com
on 17 Aug 2010 at 1:58
Any solutions for this?
Original comment by c...@ensfamily.com
on 4 Feb 2011 at 6:05
Hi. I didn't understand the problem when it showed first in August '10. After
working on WeBe++, I understand the problem. All keyboards use a semi-standard
for the key reports although they are free to use any format they like as long
as they describe it in a HID descriptor. Unfortunately, BTstack Keyboard
doesn't look at this descriptor.
I'm working on a completely new version of the package to provide the same
comfort as Apple's solution (which was released after BTstack Keyboard). In
another update, I'll add the Mouse functionality and want to add a proper HID
descriptor parser to be able to deal with all kinds of keybaord & mouse
combinations.
Original comment by matthias.ringwald@gmail.com
on 4 Feb 2011 at 9:02
Any update to this or status of the new build? Having the same issue with the
zaggmate keyboard.
Original comment by bcl...@gmail.com
on 5 Jun 2011 at 1:14
Original comment by matthias.ringwald@gmail.com
on 9 Jul 2011 at 10:09
Issue 174 has been merged into this issue.
Original comment by matthias.ringwald@gmail.com
on 9 Jul 2011 at 10:20
I have the same problems with my BT1280 keyboard.
Is there any solution or further updates in the future???
Original comment by mkc...@gmail.com
on 25 Jul 2011 at 4:04
Hi,
I talked to my boss about the possibility of combining bluetooth mouse and
keyboard on iPad for remote desktop access and he seemed interested at first,
but the no accentuation limitation and the reduced mouse speed (when combining
both mouse and keyboard at the same time) became major problems for its use at
the company. Is there a estimative to resolve these problems?
Thanks.
Original comment by saulo.pa...@gmail.com
on 11 Aug 2011 at 2:03
i am having the same problems with my zaggmate keyboard - every time i press
shift, this appears 'á' and when i press control 'à' this appears again. when
i press alt 'à' this appears, when i press control 'ã' this appears. i have
my settings set on us english. give me a break.
when i press the left alt this appears 'æ', please remind me why i bought
this. question mark. exclamation. ps i would have written all this in cap lock
to emphasis madness if i could.
Original comment by mina.s.d...@gmail.com
on 19 Aug 2011 at 7:16
Hi. Please try the 1.5 update. It tries to switch the keyboard into Boot
protocol mode, where it should behave like any other keyboard. I don't have a
ZaggMate/Logitech for testing, so please let us know if it works now (or not).
Also, please start using http://btstack.uservoice.com for issues with my
BTstack-based products on iOS.
Original comment by matthias.ringwald@gmail.com
on 21 Apr 2012 at 7:47
Original issue reported on code.google.com by
jose...@dollarphone.com
on 16 Aug 2010 at 9:52