nwg-piotr/azote

The right half of the app is unresponsive in floating mode.

snakedye opened this issue · 9 comments

Describe the bug
A clear and concise description of what the bug is.

The half of the app becomes unresponsive when it's in floating mode and the right border is set in the middle.

To Reproduce
Steps to reproduce the behavior:

  1. Launch Azote
  2. Put it in floating mode

Expected behavior
The entire app should be responsive and the border should cross it in the middle.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • Linux distribution: Arch
  • WM: sway

Azote version (please state it clearly if you use -git version):

  • v1.7.14

Additional context
Add any other context about the problem here.

It happens when the window goes full screen and back. In principle, Azote should not be full screened. Check your config. If it happens, however, you need to click a wallpaper miniature on the left side, and all the window should be accessible again.

On sway, when no additional rules applied, Azote should start like this:

image

What do you mean by no additional rules? Windows are tiled by default. I don't have any command for azote in my config.

You're right, I added a swaymsg command to enable floating on startup to my other apps, but not to Azote. This could be added here, too. For now you could just add a line similar to mine to your config:

~~for_window [title="Azote~|galculator*|pamac*"] floating enable, focus~~

You may test the commit above by installing azote-git. No additions to config required.

It does startup in floating mode but the effect described in the screenshot still persists.
image

Initially it should display 3 columns, unless you maximized it earlier, or specified "columns": "6" in ~/.config/azote/azoterc.

{
  "thumb_width": "240",
  "columns": "3",
  "color_icon_w": "100",
  "color_icon_h": "50",
  "clip_prev_size": "30",
  "palette_quality": "10",
  "tracking_interval_seconds": "5"
}

"columns": "3"

That solved the issue