> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/products/eyecommander/version-history.md). # Version History Find out about the latest changes to EyeCommander here ### 1.4.2 * Lift the max volume of the click ### 1.4.1 * [Allow users to change volume of clicking sound.](https://github.com/AceCentre/EyeCommander/issues/82) ### 1.4.0 * Fix bug that prevented users from mapping the keyboard emulator to spacebar * Add mind express option * Improve forcing run as admin workflow ### 1.3.3 * Fix bug where the app wouldn't work when the Windows User name included a space ### 1.3.2 * Improve descriptions of blink modes following feedback ### 1.3.1 * Fix bug that caused the window to resize after you opened the settings ### 1.3.0 * Add the ability to hide the sliders once you have finished using them so they don't create a cluttered UI ### v1.2.7 * You can now edit the key that is pressed in 'Keyboard Emulator' mode. ### v1.2.6 * Update links to docs * Add the ability to launch at startup ### v1.2.5 * You can now track a specific eye in all blink modes. This can be useful if a use can only make clear voluntary movements with one eye ### v1.2.4 * Can now detect when a user gazes left and right, enable in ‘blink mode’ settings area \[BETA] * Add anonymous analytics so we can understand how EyeCommander is used, [you can see them here](https://app.posthog.com/shared_dashboard/imBogUN3_VGNTZCIZjlVjKgPqzovAA) * Add visual indicator to show blink level * Drop support for Linux and MacOS ### v1.2.1 * Makes sure the users face is always in frame ### v1.2.0 * Automatically make sure that the user is an Admin, no need to ‘run as admin’ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.acecentre.org.uk/products/eyecommander/version-history.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.