Originally posted by NotMine999
View Post
Announcement
Collapse
No announcement yet.
Libinput 1.16 Will Warn You If Your System Is Too Slow
Collapse
X
-
- Likes 1
-
Originally posted by tildearrow View Post
Or if AmigaOS could do it on a single-core machine clocked in single-digit MHz!
If they have to inform us that the system is too slow, then they are doing something too heavy in the input pipeline already.
Heck, the UNIX Haters Handbook lambasted X for being such a temple to hubris and resource hog compared to highly optimized assembly things like Windows 3.1x.
Comment
-
Originally posted by NotMine999 View Post
You mean that simple concepts get lost in heavily bloated poorly written code.
In ever growing complexity, it's kinda hard to figure out what's going on sometimes.
Does not mean that code was badly written.
Like biological systems. We have a really tough time figuring out stuff, yet they were written by the masters. Evolution and time.
Does not mean that they are crappy designs.
Comment
-
Originally posted by tildearrow View PostPointer acceleration is pretty much mandatory, and there is no way to turn it off.
The acceleration profiles make no sense, like "Adaptive"? "Flat"?
Where is the "no acceleration" profile!!!
"Adaptive" on the other hand uses a device dependent acceleration method taking the current pointer velocity into account.
- Likes 1
Comment
-
Originally posted by YCbCr View Post
The "no acceleration" profile is called "Flat". It applies a constant acceleration factor regardless of the pointer velocity. Acceleration speed basically equals pointer speed with this profile.
"Adaptive" on the other hand uses a device dependent acceleration method taking the current pointer velocity into account.
No. Speed ≠Acceleration. Look here.
In the graph:
- Red is what it should be with no acceleration (≈ Vx)
- Blue is what it is with acceleration (flat profile) (≈ Vx1+a)
(where V = speed and a = acceleration)
Thankfully I found a way to disable mouse acceleration (by setting the acceleration factor to 0). However, still no way to set the pointer speed...Last edited by tildearrow; 15 November 2020, 04:12 AM.
- Likes 1
Comment
-
Originally posted by yariv View PostX11 compositors usually don't have this problem. That's because Xorg handles the input, and it does that in a separate thread.
Comment
-
Originally posted by bug77 View PostIt's not possible to write complex, multithreaded code without the "simple concepts" getting lost, the sheer number of lines of code will take care of that. It's got a little better with the advent of async/await, but not all languages support that.
Comment
Comment