asger-weirsoee / sway-smart-workspaces Goto Github PK

I tried to use your solution, but I face challenges already in the naming scheme... The readme refers to pi3-sway-workspace but the package is named sway-smart-workspace and that is also what I find as a binary.

Calling sway-smart-workspace -i 1 I get a

FileNotFoundError: [Errno 2] No such file or directory: '/home/torsten/.local/lib/python3.9/site-packages/sway_smart_workspace/templates/output'

It also seems the links in pip point to the wrong github repro.

I believe as movement of windows is something independent of sway-smart-workspaces, it should not be in the config template. I for once, got error messages as I had those movements defined within the sway config as well.
I will submit a PR for it... #3
Don't worry I know you are busy and do not expect a quick reply, good luck with your CS exams.

Hi,
I tried to get your latest patch regarding #5 working, but failed to understand how it is supposed to work.
Would be great if you could give some more information about it.

Hi,
I can't get how workspaces are supposed to act if an output is removed.
My use case:
1 use two external screens via a dock and whenever I connect to the dock, both screens get activated and the internal screen gets switched off (as I place the closed laptop in a horizontal stand anyhow).
Now, if I remove the dock and open the laptop lit, I can see that workspaces are merged however, I have now twice the same naming.
E.g. [1] on output 1 and [1] on output 2 becomes [1] [1] on output 1.
I can only address one by keyboard bindings, and the other I need to use the mouse to activate it.

I am not sure if this is the way how it is supposed to work or if I configured something wrong.

For me, I would assume, reducing the number of outputs would move all windows of the now obsolete workspaces to the workspace of the same number (or name).

Sure enough, that might only work in one way (reducing the outputs) and not the other way (extending the outputs) as sway has no way to keep track of these movements.

Using two docking station, I noticed that the names of the output ports seems not always consistent and permanent. E.g. DP-1 becomes DP-4 on the next reconnect.
That messes with the settings.
Would it be possible to use the full name, which sway usually also allows for its own output configs.
e.g. "Dell Inc. DELL U2414H 9TG463AP4L2L" instead of DP-4
That would be unique among different workplaces and the config would work more reliable.

Currently we are just uploading the package with a shell command, it would be best for future maintenance to use the official https://github.com/pypa/gh-action-pypi-publish.

Example usage of pypa/gh-action-pypi-publish would look like

- name: Publish a Python distribution to PyPI
  uses: pypa/gh-action-pypi-publish@release/v1
  with:
    user: __token__
    password: ${{ secrets.PYPI_API_TOKEN }}