Post B64VuRPEDdUTdCzBZY by snufkin_vc@mastodon.social
 (DIR) More posts by snufkin_vc@mastodon.social
 (DIR) Post #B64VuRPEDdUTdCzBZY by snufkin_vc@mastodon.social
       0 likes, 0 repeats
       
       @d6 hello! I've been working with your audio examples and and studied the synching so I wonder if a different timer port could be considered for #uxn tty?As any other devices that needs timing depends on the screen device vector, or could fall back to 1 sec resolution with the time device.Another alternative could be to implement the Screen vector in uxntty, but just call it Timer or something like that.This would allow TUI games! :)
       
 (DIR) Post #B64VuRp6fQBsvT5quO by d6@merveilles.town
       0 likes, 0 repeats
       
       @snufkin_vc This is something I've brought up with @neauoire before -- that it would be nice to have a general purpose timer device.Right now the Screen device is the only timer we have -- the Datetime device doesn't have a vector so the only way to use that is in a busy loop reading the seconds port.For right now, a Screen device with 0 height and 0 width but with a screen vector running at 60 Hz would probably be the least disruptive option. (Most ROMs that detect CLI-vs-GUI use non-zero screen size to do the detection)
       
 (DIR) Post #B64VuSA1Pev9yKsYVc by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @d6 @snufkin_vc that's what I would do, even if there's no screen, let its vector be the one.