The current behavior is that the PrintScreen key is hardcoded to call region_selection_window() function that takes a single screenshot.
Instead, upon initialization of the application, it should read settings[1] and apply hotkeys from it, you will need to handle errors, such as conflicting hotkey from another application.
In the web frontend (UI) work with Framework7 to implement hotkey input fields for video capture Start/Stop, Screenshot and Quickshot.
In the frontend create a function to capture a hotkey upon pressing the input field in the hotkey section.
The captured/changed hotkeys should be sent to the backend (Rust) using invoke() to process the changes (apply them) after user clicks on save[2] button from the frontend.
[1] The "settings" is a file created using the Tauri Plugin Store which is not yet implemented, it relates to issue https://github.com/0Ky/screenclip/issues/6
[2] The save/discard buttons for the frontend UI will most likely be implemented after #6
The current behavior is that the
PrintScreenkey is hardcoded to callregion_selection_window()function that takes a single screenshot.Instead, upon initialization of the application, it should read settings[1] and apply hotkeys from it, you will need to handle errors, such as conflicting hotkey from another application.
invoke()to process the changes (apply them) after user clicks on save[2] button from the frontend.[1] The "settings" is a file created using the Tauri Plugin Store which is not yet implemented, it relates to issue https://github.com/0Ky/screenclip/issues/6 [2] The save/discard buttons for the frontend UI will most likely be implemented after #6