would any one help explain to me why peripherals such as the

No. You seem pretty stupid and it's a rather layered, albeit simple issue.

File: 1463865604548.jpg (80KB, 560x444px) Image search: [Google]

80KB, 560x444px

>>57256178
What about my question makes me seem stupid? If I knew the answer I wouldn't post on a technology board about it. It's layered but simple doesn't that just mean you don't feel like answering it? So you use a simple question, with an admittedly simply answer, as an excuse to be not only lazy but an asshole. You're not coming out looking so good here. You were better off just not posting.

>>57256178
You are the stupid, it's not an issue at all.

>>57256232
If you can write a driver for it, you can make it happen. There are some snags, like I don't know if Xorg or whatever the fuck Windows uses allow custom keycodes. When I did this, it skipped the HID system entirely and just ran commands.

Because programs and OSes don't support custom keys. Think of it, how would any arbitrary program know what 'G1' or whatever the fuck is supposed to be?

Best thing to do is make it emulate a joystick device for separate 'keystrokes'

>>57256081
There are plenty of unused keystrokes that a standard keyboard doesn't use that you can map it to.

>>57256232
You're the lazy one.

>>57256232
>as an excuse to be not only lazy but an asshole
Yeah that was exactly it.

>>57256723
>it's not an issue just write your own driver
Thank you very much. To those just joining us that was the representative from the Lincucks community.

>>57256081
Bind the keys to F13-F24. If your macro program can't do that, then it's shit.

Now see how many programs recognize F13-F24.