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

[2.0.0-alpha5] "Move window" inconsistant behavior with regions #255

Closed
eg009 opened this Issue Oct 14, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@eg009

eg009 commented Oct 14, 2018

Made this recipe for a simple purpose of moving a window to specific region on specific screen

"parameters": {
            "window": "",
            "monitor": "\\\\.\\DISPLAY2",
            "region": "850px,800px"
          }

Behavior: window moves to region if it's not in the region. If it's already in that region it moves to another region.
More: For vertically split regions(left region of choice) it moves from left to right region. From right region moves to another screen

Expected behavior: window moves to selected region, or stays if it's already there.

@eg009

This comment has been minimized.

eg009 commented Oct 14, 2018

Current workaround: load another preset, move desired window to random region on that preset, load proper preset, move to desired region.
This one is waay to tedious, because recipe editor tends to forget user input on certain circumstances

  • the fact that you cannot change action order in editor; Workaround : config editing instead of using gui editor
@vegardlarsen

This comment has been minimized.

Member

vegardlarsen commented Oct 16, 2018

This could very well be a bug. I am tagging it and will get to it :)

@vegardlarsen vegardlarsen self-assigned this Oct 16, 2018

@vegardlarsen vegardlarsen added the bug label Oct 16, 2018

@vegardlarsen vegardlarsen added this to the 2.0.0 milestone Oct 16, 2018

@vegardlarsen vegardlarsen modified the milestones: 2.0.0, 2.0.0-beta.3 Nov 9, 2018

@vegardlarsen

This comment has been minimized.

Member

vegardlarsen commented Nov 12, 2018

Thank you for reporting this issue. While I was working on this, I found 3 other crashing bugs that needed fixing.

This has been fixed and will be in 2.0.0-beta.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment