aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2025-08-22 17:40:54 +0300
committerIvan Molodetskikh <yalterz@gmail.com>2025-08-22 17:41:52 +0300
commit58290516c7061deeedab39184853f47b727a5561 (patch)
tree7695da766b6454b30d30dd03df11b049708c903e
parent210d5e90fe00ae9add5d841e1752b7f8c4a639a7 (diff)
downloadniri-58290516c7061deeedab39184853f47b727a5561.tar.gz
niri-58290516c7061deeedab39184853f47b727a5561.tar.bz2
niri-58290516c7061deeedab39184853f47b727a5561.zip
wiki/Animation-Timing: Add two nbsps
The 170 Hz one was at the exact breaking point for me.
-rw-r--r--docs/wiki/Development:-Animation-Timing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/wiki/Development:-Animation-Timing.md b/docs/wiki/Development:-Animation-Timing.md
index e9d5f373..6788ac42 100644
--- a/docs/wiki/Development:-Animation-Timing.md
+++ b/docs/wiki/Development:-Animation-Timing.md
@@ -1,7 +1,7 @@
> *Time, Dr. Freeman? Is it really that... time again?*
A compositor deals with one or more monitors on mostly fixed refresh cycles.
-For example, a 170 Hz monitor can draw a frame every ~5.88 ms.
+For example, a 170 Hz monitor can draw a frame every ~5.88 ms.
Most of the time, the compositor doesn't actually redraw the monitor: when nothing changes on screen (e.g. you're reading a document and aren't moving your cursor), it would be wasteful to wake up the GPU to composite the same image.
During an animation however, screen contents do change every frame.