Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests for sway #121

Open
acrisci opened this issue Aug 18, 2019 · 6 comments
Open

Tests for sway #121

acrisci opened this issue Aug 18, 2019 · 6 comments

Comments

@acrisci
Copy link
Member

acrisci commented Aug 18, 2019

Since sway is officially supported by this library, we should have tests that test it against a running sway binary.

@nwg-piotr
Copy link

nwg-piotr commented Aug 27, 2019

On Arch Linux I use an old -git package, which includes the "add event_state_mask and symbols to binding info" commit, and it works well. Tonight I built a Void Linux package v2.0.1, and it crashes for me on the 'binding' event again. For now no idea what's happening. On i3 everything works well.

@acrisci
Copy link
Member Author

acrisci commented Aug 27, 2019

The binding event works fine for me.

@nwg-piotr
Copy link

Strange... I'll try to take a closer look on Arch tonight.

@nwg-piotr
Copy link

Alright, there was a mess in virtual environments. After cleaning it up, I'm having some other difficulties with my code, but the binding event does not crash any longer. Sorry for my mistake.

@Galicarnax
Copy link

When running under i3, i3ipc.Connection().get_tree() returns a single object representing the root container. When used under sway, get_tree() returns a linear list of all containers (root, workspaces, windows). Using i3ipc version 2.2.1-1 under Arch in both cases. No mention in the docs that get_tree() might behave differently under i3 and sway.

@Galicarnax
Copy link

Never mind, it was an issue with a 3rd-party library, not i3ipc-python. Sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants