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

Issue with Window Alignment in Kap #1187

Open
johnlin10 opened this issue Sep 6, 2023 · 3 comments
Open

Issue with Window Alignment in Kap #1187

johnlin10 opened this issue Sep 6, 2023 · 3 comments

Comments

@johnlin10
Copy link

macOS version: MacOS 14 Public Beta 4
Kap version: 3.6.0

Description

The issue I'm encountering pertains to the alignment of the recording window in Kap. When performing window recording, the dotted line outlining the selected window is misaligned with the window's edge, resulting in a visual deviation in the recorded video.

Steps to reproduce

  1. Launch Kap.
  2. Click on "Window Recording."
  3. Select a specific window.

Current behavior

Upon selecting a window for recording, Kap automatically frames the window. However, the dotted line that outlines the window is not properly aligned with the window's edge. This misalignment causes the recorded video to include the misframed line.

Expected behavior

When using the Window Recording feature and selecting a window, the preview frame line should align precisely with the window's edge, ensuring that it is no longer within the recording area. Consequently, recording should take place within the confines of the preview frame line.

Workaround

As of now, I have not identified a direct solution to the problem. The temporary workaround is to manually select the recording area.

Please note that I am using a beta version of macOS, and it's possible that this may be a contributing factor to the issue. I hope that this problem can be resolved in future updates. Thank you for your attention to this matter.

@sveggiani
Copy link

Hi @johnlin10 , the same is happening to me.
I'm on macOS Ventura and started having this issue when upgrading from 13.5 to 13.5.2 a couple days ago.

@sveggiani
Copy link

Circlying back on this, I just found that the issue in my case seems to be that I'm using Stage Manager. If I deactivate that everything seems to work fine again.
cc: @johnlin10

@johnlin10
Copy link
Author

Thank you @sveggiani for providing a better solution.
I've been following this issue for some time.

Indeed, as you mentioned, the problem arises due to the Stage Manager.

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

2 participants