Plover Per-Application State
Plover plugin to make translation state function per application window and tab.
DISCLAIMER: This plugin is still WIP and will cause Plover to function incorrectly under some circumstances.
Installation
-
Navigate to the installation directory for Plover and open a terminal / command prompt.
-
Run:
<exe_name> -s plover_plugins install -e plover-per-application-stateThe plover-application-controls plugin should be installed automatically as a dependency.
-
Restart Plover.
-
Configure > Plugins > Enable both
application_controlsandper_application_state.
To disable the plugin at any point, disable per_application_state.
Disabling application_controls will prevent the plugin from being able to detect the currently active window.
Important Dictionary Setup:
Any dictionary entries which result in a window being switched will need to be modified to include
{PLOVER:per_application_state:prevent_merge} at the start of the translation. This is to ensure that the plugin
correctly reloads state when the window is switched.
For example {#Control(tab)} will need to be modified to {PLOVER:per_application_state:prevent_merge}{#Control(tab)}.
This is NOT required for any {PLOVER:application:} commands from
plover-application-controls.
Commands:
The {PLOVER:per_application_state} command can be used to control state management. It takes a subcommand as its first
argument, with further arguments separated by :.
For example, {PLOVER:per_application_state:clear_all} will clear all state.
| Window Command | Description | Arguments |
|---|---|---|
| clear | Clear the translation state for the current window tab | |
| clear_all | Clears the current and stored translation states for all windows | |
| clear_window | Clears the current and stored translation states for the current active window | |
| prevent_merge | Temporarily prevents state from being merged when a title changes as a result of a stroke |
Metadata
Release files for plover-per-application-state 1.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plover-per-application-state-1.3.1.tar.gz | 18.9 kB | Without provenance | Details for plover-per-application-state-1.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plover_per_application_state-1.3.1-py3-none-any.whl | Python 3 | none | any | Details for plover_per_application_state-1.3.1-py3-none-any.whl |
Total release size: 40.9 kB
Release files / plover-per-application-state-1.3.1.tar.gz
| Download URL | plover-per-application-state-1.3.1.tar.gz |
|---|---|
| Size | 18.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
121c34ed26bfa9762be002516a58307d99246a30f049eae062bd2343aedb5829
|
|
BLAKE2b-256 checksum How to use checksums |
0c58c46333472821856e2446ba3ed3b22a596f2d78894c6e6c4532a939fabc9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / plover_per_application_state-1.3.1-py3-none-any.whl
| Download URL | plover_per_application_state-1.3.1-py3-none-any.whl |
|---|---|
| Size | 22.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
944bd2bee374284ba84ea35f66401ae2833b39709ca2846ed326f51b89760235
|
|
BLAKE2b-256 checksum How to use checksums |
7983ea682a7ba2bd90261c6a1e0e9d4c1509af15b14c5fa0e3bcc4629eba7387
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for plover-per-application-state 1.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.