Calc84, our methods are contradicting.  Which is correct?

Edit: calc84's right.   I forgot he stored them little endian. (My post has been edited.)

Oh ok, I guess I might have misunderstood Quigibo comments when we discussed about lists storage

what about storing several numbers in a list, though, do you do

{1,2,5,65,127,0,26,114->L1

?

That's where it's hard.
I guess you could do this:

[01020541001A72->GDB1
For(A,0,7
{GDB1+A}->{L1+A}
End

This is where the problem is: You have to store it in Hex, because so far this is all Axe supports.  However, eventually normal lists will be available.

=======
Edit:

Holy crap really?
Also, how do you retrieve them?

{L1+1}*256+{L1}->A

really Ztrumpet? Didn't Quigibo said something about only be able to store lists like this:

[DBCE9BA65A764528->L1

?

Nah, that's just some fancy stuff involving list compression.
(Hex stores better than a bunch of 1->{L1}:2->{L1+1}...9001->{L1+200}.)

Aw, it didn't link to the right page.  Let me try it without translating.

Edit: Here: http://ti.bank.free.fr/index.php?mod=archives&ac=voir&id=620
I think it's 2.43, though the screenie says 2.41...

Wow.  That's pretty cool, but I think the blue under the Axe doesn't look as well as without the blue. =\
I, however, think there should be some color there. 

The asm layout is completely different, you have to activate key groups, then you get back a byte with different bits set to represent different keys.  It appears to be the xLib layout, though, at first glance.

Yup, I'm pretty sure it is the xLib layout.  I've been using the xLib readme for key codes, so, yeah...

*Ztrumpet prints this out...

That sounds cool!  I like that idea.  Bring on the '#include's!