mirror of
https://github.com/kangyu-california/PersistentWindows.git
synced 2025-05-11 04:55:39 +02:00
update readme, help
This commit is contained in:
parent
0160e04b21
commit
17b5ae0b48
2 changed files with 3 additions and 2 deletions
2
Help.md
2
Help.md
|
@ -76,7 +76,7 @@
|
|||
* A webpage commander window captures command shortcuts (which are carefully designed to be done single handedly) and translates them to the underlying web browser window, maximizing the efficiency of web browsing.
|
||||
* Press Alt + W to activate/deactivate the webpage commander window.
|
||||
* Once activated, Press Z to toggle the size of commander window (the 8x8 tiny sized commander window is strongly suggested),
|
||||
and now enjoy one-letter command shortcuts on all major web browsers (Chrome, Edge, Firefox, Opera, Brave, Vivaldi etc)
|
||||
and now enjoy one-key command shortcuts on all major web browsers (Chrome, Edge, Firefox, Opera, Brave, Vivaldi etc)
|
||||
| Command shortcut| Translation | Meaning|
|
||||
| --- | --- | --- |
|
||||
| 1-8 | Ctrl + #n | select tab #n
|
||||
|
|
|
@ -86,7 +86,8 @@ Choose one of the two options:
|
|||
- PersistentWindows periodically checks the github repository for software version upgrades. This can be disabled in the options menu.
|
||||
|
||||
## Known Issues
|
||||
- **Multiple invocations of "Restore windows from disk" might be needed in order to recover all missing windows after system startup.**
|
||||
- PersistentWindows may malfunction on fractionally scaled display (such as 125%, 150% etc), it is strongly suggested to override the high DPI scaling property of PersistentWindows.exe to "Application" via Properties->Compatibility->Change high DPI settings dialog from explorer, user needs to capture windows to disk immediately after relaunching PW w/ the new DPI setting.
|
||||

|
||||
- PersistentWindows can get stuck in a "busy" state (with a red icon in the System Tray) during a restore if one of the windows becomes unresponsive. You may find out the culprit window in Task Manager using "Analyze wait chain". The unresponsive app might need an immediate hot-upgrade, or need to be killed to let PersistentWindows proceed
|
||||
|
||||
<img src="https://user-images.githubusercontent.com/59128756/184041561-5389f540-c61a-4ee7-90ff-f9f725ba3682.png" alt="image" width="500"/>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue