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
[Bug]: Chat window off screen #474
Comments
The Codeium for Xcode fork only supports the suggestion feature. Clicking the widget won't open the chat window. If you need the chat feature, please use the Copilot for Xcode, which also supports Codeium as a provider of suggestion. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before Reporting
What happened?
I am using Kodium for Xcode on a dual display system connected to my computer. Recently I had changed the resolution of one of the monitors and then changed it back to 1920 by 1080. Now, when using Codium, I see the little widget, either at the bottom or next to the text, as set by the application Clicking on the widget the chat window never appears. The active window goes inactive, indicating the chat window appeared but according to what I can find debugging, it is set to minus 1361 on the and is somewhere off screen.
I tried uninstalling and then reinstalling that didn't work. I tried changing the resolution of the displays. I tried disconnecting and reconnecting displays one at a time.
So somewhere in the code it is not being clamped to the screen it is located on.
How to reproduce the bug.
Not sure how to reproduce it, but I believe it had something to do with changing the resolution on one of the monitors. I downloaded the Xcode project and it compiled okay but I get lost in the filer window positioning.
Relevant log output
No response
macOS version
14.4
Xcode version
15.3
Copilot for Xcode version
0.30.5
The text was updated successfully, but these errors were encountered: