2 ms·
For events that happen that often, signals are not the right tool/implementation for the job. Deciding on a communication mechanism is a game of balances and t
by freedomben 4y ago
For events that happen that often, signals are not the right tool/implementation for the job. Deciding on a communication mechanism is a game of balances and trade-offs depending on your needs. HTTP is much slower than some more complex RPC mechanisms, but it's fast enough for most applications. if somebody were blasting enormous amounts of data through it, you wouldn't criticize HTTP as too slow, you'd change to a more appropriate protocol that forces more complexity on the application but is more efficient with time and space. I think you should do the same here and use a different communication mechanism than signals.
FWIW, I did some pretty intense real time animation in Qt about 10 years ago, and even on the crap hardware at the time I had no issue using signals to hook into mouse move events (which happen often and quickly sometimes).