« previous next »
Pages: 1 [2]   Go Down

Author Topic: TI & Lua  (Read 10543 times)

0 Members and 3 Guests are viewing this topic.

Offline aeTIos

  • Nonbinary computing specialist
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3915
  • Rating: +184/-32
    • View Profile
    • wank.party
Re: TI & Lua
« Reply #15 on: June 17, 2012, 06:46:43 am »
Maybe TI-Planet guys can ask for direct input?
Logged
I'm not a nerd but I pretend:

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: TI & Lua
« Reply #16 on: June 17, 2012, 07:16:19 am »
In fact, they did so a year ago...
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline Jim Bauwens

  • Lua! Nspire! Linux!
  • Editor
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1881
  • Rating: +206/-7
  • Linux!
    • View Profile
    • nothing...
Re: TI & Lua
« Reply #17 on: June 17, 2012, 07:26:27 am »
Direct input in what sense ?
Logged

Offline Lionel Debroux

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2135
  • Rating: +290/-45
    • View Profile
    • TI-Chess Team
Re: TI & Lua
« Reply #18 on: June 17, 2012, 07:44:35 am »
I think that "direct input" for the Nspire means what it means in basically all other TI graphing calculators (and undoubtedly in some graphing calculators for other manufacturers): some form of direct getKey ;)

Double bonus points for providing both a slow getKey and a fast getKey. On the TI-68k, the former would be represented by ngetchx() or GKeyIn(NULL, 0), which also takes care of other things, while the latter would be represented by the rather fast OSdequeue(kbd_queue()).
« Last Edit: June 17, 2012, 07:46:29 am by Lionel Debroux »
Logged
Member of the TI-Chess Team.
Co-maintainer of GCC4TI (GCC4TI online documentation), TILP and TIEmu.
Co-admin of TI-Planet.

Offline aeTIos

  • Nonbinary computing specialist
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3915
  • Rating: +184/-32
    • View Profile
    • wank.party
Re: TI & Lua
« Reply #19 on: June 17, 2012, 09:15:19 am »
Hmm, yeah. Some form of the Axe getkey would be cool :D And is pretty much possible I guess. (Axe has getkey(keycode) just like basic but 120 times faster).
Also no key delay function would be cool.
Logged
I'm not a nerd but I pretend:

Offline Nick

  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1166
  • Rating: +161/-3
  • You just got omnom'd
    • View Profile
    • Nick Steen
Re: TI & Lua
« Reply #20 on: June 17, 2012, 09:58:35 am »
well, the only thing I find sad is that they made it event based.. loop based is much more flexible (imo) than event based, but i guess that's completely personal.

and about that getkey, it would be nice, but the way it is made now (with on.charIn()) it would conflict.. so that won't come i think
Logged

Offline Jim Bauwens

  • Lua! Nspire! Linux!
  • Editor
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1881
  • Rating: +206/-7
  • Linux!
    • View Profile
    • nothing...
Re: TI & Lua
« Reply #21 on: June 17, 2012, 10:14:44 am »
@Lionel, aeTIos
Okay, I see your point there. Indeed, it would be nice to have some other key input stuff. For example, you can not catch many ctrl-[a-z] keys. A bit annoying, if you want to assign hotkey's to certain things.

Nick, in a sense you can run non event based stuff on a TI-Nspire. I've developed a small program to do that, and it works pretty good. Just did not have much time to work on it.
Logged
Pages: 1 [2]   Go Up
« previous next »