I'm trying to get wayland clients to pace based on frame callbacks, and it's showing some interesting quirks of our client implementation.

Right now when I start terminology it registers an animator for the cursor immediately, even if it's not displaying one. This will remain registered until I mouse in, then out, then back into the app.

That results in running the timer tick thread currently, but when ticking off frame callbacks it means both the compositor and the client will need to wake 60 times per second when there's nothing to display. Not ideal for battery life...