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

i3 readme update #200

Merged
merged 4 commits into from Nov 6, 2017

Conversation

Projects
None yet
3 participants
@McKean
Copy link
Contributor

McKean commented Oct 23, 2017

So basically peek works very nicely with i3 if you just stack it with the intended window you want to record.
Tested and works fine on my setup, as I've read many people have issues with i3 and peek and I had too, I think it's best addressed here.

Thank!

@sQVe

This comment has been minimized.

Copy link

sQVe commented Oct 26, 2017

I cannot get this to work. The instructions are a bit fuzzy, what do you exactly mean by "stack it with the intended window"?

@phw

This comment has been minimized.

Copy link
Owner

phw commented Oct 26, 2017

I wanted to test this myself before merging anything, but don't have the time for it right now. But for all that I know i3 does not support the X shape extension, and without this the click through cannot work AFAIK. See also i3/i3#2742 .

@McKean Is clicking and interacting with the recorded content possible for you or just the recording? Do you have a compositor (e.g. compton) running?

@sQVe

This comment has been minimized.

Copy link

sQVe commented Oct 26, 2017

I'm not getting it to click through eventhough I'm floating both windows with peek on top. I'm also having issues with the tmp file having no content in it when I use i3.

@McKean

This comment has been minimized.

Copy link
Contributor

McKean commented Oct 26, 2017

@sQVe see this screenshot:
screenshot
@phw yes I'm using compton, I'm not sure if it works without. Clicking works perfectly fine too. I can upload a video if this would help.

One thing that would be beneficial is to be able to start peek without that top bar, that way it would record the whole window which is stacked (you can see in the screenshot that it will not capture the top part). Other than that it works really well.

edit:
@phw I just tested disabling compton and it worked!

@McKean

This comment has been minimized.

Copy link
Contributor

McKean commented Oct 26, 2017

i3 stacked windows no compton:
screenrecording

@sQVe

This comment has been minimized.

Copy link

sQVe commented Oct 27, 2017

I can now confirm that using either stacked, tabbed or floating both windows (peek and the window to be recorded) in i3 is working to record with peek 👍.

@McKean

This comment has been minimized.

Copy link
Contributor

McKean commented Oct 27, 2017

@sQVe great to hear, instead of using the two floating windows approach I would recommend using the scratchpad method, where you put Peek into a scratch pad if you want to have a strictly defined area to record.

@phw phw added this to the 1.2.0 milestone Oct 30, 2017

@phw

This comment has been minimized.

Copy link
Owner

phw commented Nov 6, 2017

I am not an i3 user, but I think now I get it. While click-through is not working on i3, i3 is flexible enough to do with Peek whatever you want, also having it ignore Peek's wish to be always on top and send it to that hidden scratchpad workspace where it is not visible but still maintains its coordinates. Is this about right?

Thanks for this addition to the documentation.

@phw phw merged commit 6b5f190 into phw:master Nov 6, 2017

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@sQVe

This comment has been minimized.

Copy link

sQVe commented Nov 6, 2017

@phw That is correct. There are plenty of different ways for it to work with i3. 👍

@McKean

This comment has been minimized.

Copy link
Contributor

McKean commented Nov 6, 2017

@phw yeah that's pretty much it. Also the reason why I'm requesting: #203
But perhaps I should just try and contribute towards such a feature myself :)

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