Handling command line inputs with ASCII values > 128 about g810-led

[larsnaesbye]

I could live with using a standard moniker instead, like 'aelig'. Everything is better than having to remember it's the semicolon or whatever.

[MatMoul]

Just use a \ before the char...
for tilde, you can use : g810-led -k \~ ff0000
always with tilde it's possible to add a second possibility as ex : g810-led -k tilde ff0000

[noisycat]

tilde? He's talking about ASCII+145, not ASCII+126 (reference: http://www.theasciicode.com.ar/extended-ascii-code/latin-diphthong-ae-lowercase-ascii-code-145.html )

+145 is outside of the (char* argv[]) input that main gets. And instead of just using complements, since most of those special characters aren't in the ASCII table, it starts making sense to have the discussion.

[MatMoul]

I have used the tilde sample to show that you can have multiple definition of a key
I just tested to add æ in Keyboard::parseKey and it work from command line without \

[MatMoul]

Can I close this issue ?

[larsnaesbye]

Sure, if it works I see no reason not to close it :-)