Wayland

Due to the varying levels of support for Wayland among different distributions, pot itself cannot achieve perfect compatibility. Here are some solutions to common issues that can be implemented through proper configuration, allowing pot to run perfectly on Wayland.

Shortcut can't be used

Due to the fact that Tauri's shortcut scheme does not support Wayland, the shortcut settings within the pot application cannot be used under Wayland. You can set system shortcuts to trigger pot by sending a request with curl. For more details, please refer to External Calls.

Screenshot cannot be used

In some pure Wayland DE/WM (such as Hyprland), the built-in screenshot feature of pot cannot be used. In this case, you can use other screenshot tools instead. For more details, please refer to OCR without internal screenshot.

Below is an example of configuration in Hyprland (capturing screenshots using grim and slurp):

bind = ALT, X, exec, grim -g "$(slurp)" ~/.cache/com.pot-app.desktop/pot_screenshot_cut.png && curl "127.0.0.1:60828/ocr_recognize?screenshot=false"
bind = ALT, C, exec, grim -g "$(slurp)" ~/.cache/com.pot-app.desktop/pot_screenshot_cut.png && curl "127.0.0.1:60828/ocr_translate?screenshot=false"

Other desktop environments/window managers also have similar operations.

The translation window follows the mouse position

Due to the current inability of pot to obtain correct mouse coordinates under Wayland, its internal implementation cannot work. For certain desktop environments/window managers, window rules can be set to achieve window following mouse position. Here we take Hyprland as an example:

windowrulev2 = float, class:(pot), title:(Translator|OCR|PopClip|Screenshot Translate) # Translation window floating
windowrulev2 = move cursor 0 0, class:(pot), title:(Translator|PopClip|Screenshot Translate) # Translation window follows the mouse position.