I’ve just started looking at how the repeat works for the buttons. The
on XX button block has
repeat on it. The first two have obvious semantics but I wasn’t sure how
repeat worked. In particular, I was concerned that it might be influenced by the settings of the o/s, possibly with per user customisation.
The values look consistent across simulator (beta beta,
0.14.2 5.21.5) and hardware which is nice. They also don’t appear to vary based on using mouse vs space bar in sim. Some representative values follow:
delay: 515 repeat 1: 20 repeat 2: 41 delay: 517 repeat 1: 38 repeat 2: 21 delay: 507 repeat 1: 41 repeat 2: 20
From the empirical data it looks like the repeat rate is both not guaranteed and unlikely to consistently match the set rate? Is the granularity the
interval or 20ms? There’s not much going on in my code at least for first few repeats so I don’t think I can attribute the early jitter here to load from stuff going on in the app?
What’s the philosophy behind these default values? They look like values chosen for typing on a (QUERTY or similar) keyboard but Arcade is a keyboard-less environment. I’m not sure I see the justification for the lengthy
For my intended use I think I need to reduce the
delay to be the same as the
interval but I don’t think I can do this in Blocks?
I’d be interested to hear what others think of this feature and how they use it in their Arcade applications.