-
Notifications
You must be signed in to change notification settings - Fork 20
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
Shortcut keys not working properly #26
Comments
Thank you for using Formation Studio. Which OS are you using? |
From the two machines I used, one had Windows 10, the other Windows 11 |
@andeyv I will have to look deeper into the issue. I started developing a possible fix today but in the mean time you can either:
|
i am also having this issue, specifically with the alt key |
@dresis @Razieleron Could you try installing the 0.6.x-fix branch to see if the issue is resolved? I want to be sure the issue is resolved before publishing the new release. You can use the commands below. pip uninstall formation-studio
pip install git+git://github.com/ObaraEmmanuel/Formation.git@v0.6.x-fix#egg=formation-studio |
I have published the release so updating to the latest version should hopefully resolve the issue. |
Thank you! Sorry for not being able to check
…On Thu, Jan 11, 2024, 3:54 PM Emmanuel Obara ***@***.***> wrote:
I have published the release so updating to the latest version should
hopefully resolve the issue.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVXBOOOMKBZMICSQBW4NAYLYOB3RVAVCNFSM6AAAAAA7Z5EWV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGE2TGNBSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@Razieleron no worries. Let me know if the issue is not resolved. |
I downloaded Formation Studio in an environment I created with Anaconda. When I open it, it seems as if Formation Studio always seems to be thinking the 'Alt' key is being pressed, so I run into two issues:
I was able to replicate this in 3.8 and 3.11. Also this is something I have seen in 2 machines of mine already, thinking maybe one of them had a broken keyboard lol
The text was updated successfully, but these errors were encountered: