
Bluetooth keypad conflict w/ orig. keypad in keymapping?
Bluetooth keypad conflict w/ orig. keypad in keymapping?
I'm wondering if I buy a separate bluetooth keypad whether or not it'll have any key mapping conflicts with my keyboards numeric keypad. I'm pretty sure the answer is no since you can make new key maps with letters by capitalizing them, but I just wanted to be sure before I invest. Shortest answer wins a laugh. Thanks. 

Re: Bluetooth keypad conflict w/ orig. keypad in keymapping?
At least in Windows
There is never distinction
Between HID's
(Aiming for shortest answer, at least it's a haiku)
Long explanation:
Human Interface Devices are typically not recognized as unique. Your multiple keyboards send identical keystrokes, it's not like MIDI where you can operate on different channels or interfaces to differentiate. In most cases [one exception I can think of is some laptops] even the state of the numlock key is shared across all keyboards.
You might be able to hack around this limitation using something like Wunderworks Teamplayer, but this seems like alot of work.
Best of luck.
--Pip
There is never distinction
Between HID's
(Aiming for shortest answer, at least it's a haiku)
Long explanation:
Human Interface Devices are typically not recognized as unique. Your multiple keyboards send identical keystrokes, it's not like MIDI where you can operate on different channels or interfaces to differentiate. In most cases [one exception I can think of is some laptops] even the state of the numlock key is shared across all keyboards.
You might be able to hack around this limitation using something like Wunderworks Teamplayer, but this seems like alot of work.
Best of luck.
--Pip
Re: Bluetooth keypad conflict w/ orig. keypad in keymapping?
Thanks for the response. Do you know of any type small Midi or non-midi controller which I could use to program shortcut keys besides a Shuttle pro 2? (I've already got one but need more buttons) Something along the same lines as that possibly? Thanks again.