🌲Major Bug Fixes & Stability Improvements | v4

1. Writing Tools now supports Linux (run it from source), all thanks to @momokrono 's work making Writing Tools platform agnostic using the pynput library.

2. Fixed a bug where Writing Tools would stop recognising the hotkey after you lock & unlock your PC. Other bugs/wonkiness relating to the hotkey may also be fixed. This is also thanks to @momokrono 's migration to the stable pynput.

3. Fixed a bug where Writing Tools may not have worked in Microsoft Word due to a very quick sleep timer not working with Word's text system (Credit: @theJayTea ).

4. Improved the system prompts so that the model does not respond/answer the text in the prompt! (Credit: @theJayTea )

5. Fixed the Settings UI being slightly broken & too long, clipping out of smaller/lower resolution screens (Credit: @theJayTea ).

6. Fixed the Error pop-up not displaying when the LLM can't do what you requested with the text, with the internal error message replacing the text instead. (Credit: @theJayTea )

7. Fixed a new line being added after using Writing Tools. (Credit: @theJayTea )

6. Fixed an issue where Writing Tools would not quit if you closed it during onboarding (Credit: @momokrono ).

7. Fixed an issue where the Describe your change... text box may not automatically get focus on slower devices (Credit: @momokrono )

Thanks again to @momokrono's amazing work with the Linux port and keyboard library migration — they did a remarkable job :)

---

⬆️ Update Instructions:

Simply replace your old Writing Tools folder with the new one!

🐞 Known Issues

1. (Potential fix being investigated) On some devices, Writing Tools does not work correctly with the default hotkey.
   To fix it, simply change the hotkey to ctrl+` or ctrl+j and restart Writing Tools.
   PS: If a hotkey is already in use by a program or background process, Writing Tools may not be able to intercept it. The above hotkeys are usually unused.

2. The initial launch of the Writing Tools.exe might take unusually long — this seems to be because AV software extensively scans this new executable before letting it run. Once it launches into the background in RAM, it works instantly as usual.