You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Start API Reference page
Documentation of keep.running, keep.presenting and dbus related
things.
* Switch from napoleon to numpydoc. This looks nicer for few reasons.
(1) The napoleon adds bullet points to parameter lists. These are
unwanted.
(2) Napoleon adds an en dash between parameter type and description,
which is unwanted.
(3) Napoleon makes description start from the same line as the
parameter name and type. This is also unwanted.
* Update Sphinx~=5.0 -> ~=7.0
* Update myst_parser~=1.0.0 -> ~=2.0.0
* Add bunch of cross-links.
Dbus adapters are an advanced concept of wakepy. They would be used in such a case where wants to use other D-Bus python library than the default (which is `jeepney <https://jeepney.readthedocs.io/>`_).
Copy file name to clipboardExpand all lines: docs/source/modes.md
+42-7Lines changed: 42 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,10 +31,8 @@ with keep.running() as m:
31
31
(keep-running-mode)=
32
32
## keep.running
33
33
34
-
35
-
**Does keep.running prevent manually putting system to sleep?** All the methods, if not otherwise specified, only prevent the *automatic, idle timer timeout based* sleeping, so it is still possible to put system to sleep by selecting Suspend/Sleep from a menu, closing the laptop lid or pressing a power key, for example. One exception is systemd mask method on Linux, which prevents suspend altogether.
36
-
37
-
**Can I lock my computer after entered `keep.running` mode?**: Yes, and you probably should, if you're not near your computer. The programs will continue execution regardless of the lock.
34
+
While `keep.running` mode is activated, the system may not automatically go to sleep (or
35
+
suspend) meaning that programs will continue running and can use CPU.
| Windows | * |[SetThreadExecutionState](#keep-running-windows-stes)|
45
43
44
+
45
+
Does keep.running prevent manually putting system to sleep?
46
+
: Only the automatical, idle timer timeout based sleep / suspend is prevented; Will not
47
+
prevent user manually entering sleep from a menu, by closing a laptop lid or by pressing
48
+
a power button, for example.
49
+
50
+
Can I lock my computer after entered `keep.running` mode?
51
+
: Yes, and you probably should, if you're not near your computer. The program will
52
+
continue execution regardless of the lock.
53
+
54
+
What about automatical lockscreen / screensaver?
55
+
: The system may still automatically log out user, enable lockscreen or turn off the
56
+
display. Automatic lock screen is not guaranteed, but it is not prevented in any way.
57
+
58
+
What happens id the process holding the lock dies?
59
+
: The lock is automatically removed. There are no methods in keep.running mode which for
60
+
example would perform system-wide configuration changes or anything which would need
61
+
manual reversal.
62
+
63
+
64
+
46
65
(keep-presenting-mode)=
47
66
## keep.presenting
48
67
68
+
While `keep.presenting` mode is activated, the system may not automatically go to sleep (or
69
+
suspend) meaning that programs will continue running and can use CPU. In addition to
70
+
that, automatic start of screensaver & screenlock are prevented, meaning that you can
71
+
show content in the `keep.presenting` mode.
49
72
50
-
**Does keep.presenting prevent manually putting system to sleep?** All the methods, if not otherwise specified, only prevent the *automatic, idle timer timeout based* sleeping and screensaver/screenlock, so it is still possible to put system to sleep by selecting Suspend/Sleep from a menu, closing the laptop lid or pressing a power key, for example. It is also possible to manually start the screenlock/screensaver while presenting mode is on.
51
-
52
-
**Is my computer locked automatically in `keep.presenting` mode?**: No. Entering a screenlock automatically would stop presenting the content.
0 commit comments