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

Menu mnemonics (alt-f, etc) getting typed into the editor #3057

Closed
Akarshit opened this Issue Jan 24, 2015 · 9 comments

Comments

Projects
None yet
4 participants
@Akarshit
Member

Akarshit commented Jan 24, 2015

When pressing shotcuts for the menubar , the key also gets typed into the editor.
Steps to reproduce :

  1. Open processing
  2. Press Alt + F
    The file menu opens but "f" gets typed into the editor.
@hamoid

This comment has been minimized.

Show comment
Hide comment
@hamoid

hamoid Jan 28, 2015

Contributor

I don't remember ever having such shortcuts in Processing under Linux. Are those shortcuts OS dependent?
What I have seen lately is that sometimes I press CTRL+X and the console prints "cut".

Contributor

hamoid commented Jan 28, 2015

I don't remember ever having such shortcuts in Processing under Linux. Are those shortcuts OS dependent?
What I have seen lately is that sometimes I press CTRL+X and the console prints "cut".

@Akarshit

This comment has been minimized.

Show comment
Hide comment
@Akarshit

Akarshit Jan 28, 2015

Member

They were added recently and i also saw the that cut is getting printed in the console.
But i am not able to build processing right now so i cant do anything about it.

Member

Akarshit commented Jan 28, 2015

They were added recently and i also saw the that cut is getting printed in the console.
But i am not able to build processing right now so i cant do anything about it.

@GKFX

This comment has been minimized.

Show comment
Hide comment
@GKFX

GKFX Jan 28, 2015

Contributor

@hamoid I have fixed the "cut" error. I haven't committed yet because the latest code won't build on my machine so I can't do good tests.

Contributor

GKFX commented Jan 28, 2015

@hamoid I have fixed the "cut" error. I haven't committed yet because the latest code won't build on my machine so I can't do good tests.

@hamoid

This comment has been minimized.

Show comment
Hide comment
@hamoid

hamoid Jan 28, 2015

Contributor

@GKFX great! I know there are many changes going on at the moment.
BTW. While fixing this, did you notice why it could happen that CTRL+C and CTRL+X suddenly would stop working? I can not reproduce it, but lately it has happened two or three times. I can solve it by closing and opening Processing. I suspected that the println("cut") was there to debug this issue I'm having at times.

Contributor

hamoid commented Jan 28, 2015

@GKFX great! I know there are many changes going on at the moment.
BTW. While fixing this, did you notice why it could happen that CTRL+C and CTRL+X suddenly would stop working? I can not reproduce it, but lately it has happened two or three times. I can solve it by closing and opening Processing. I suspected that the println("cut") was there to debug this issue I'm having at times.

@GKFX

This comment has been minimized.

Show comment
Hide comment
@GKFX

GKFX Jan 28, 2015

Contributor

No, I didn't. The println("cut"); was added to debug moving from a cut ActionListener to a full CutAction, which allows menu dimming. When you say stop working, do you mean they went dim/inactive when they should have remained active? They are supposed to only gray out when there is no text selected.

Contributor

GKFX commented Jan 28, 2015

No, I didn't. The println("cut"); was added to debug moving from a cut ActionListener to a full CutAction, which allows menu dimming. When you say stop working, do you mean they went dim/inactive when they should have remained active? They are supposed to only gray out when there is no text selected.

@hamoid

This comment has been minimized.

Show comment
Hide comment
@hamoid

hamoid Jan 28, 2015

Contributor

It didn't occur to me to look at the menues to see if they were dimmed/inactive. I would just press CTRL+X for instance, but nothing would happen. The text would remain there, and the clipboard would keep it's old value. If it happens again I'll look at the menues.

Contributor

hamoid commented Jan 28, 2015

It didn't occur to me to look at the menues to see if they were dimmed/inactive. I would just press CTRL+X for instance, but nothing would happen. The text would remain there, and the clipboard would keep it's old value. If it happens again I'll look at the menues.

@hamoid

This comment has been minimized.

Show comment
Hide comment
@hamoid

hamoid Jan 28, 2015

Contributor

I think I found it. I click on the Edit menu to open it, click again to close it without choosing anything. CTRL+X does not work. Click twice again on Edit, CTRL+X is back.

Contributor

hamoid commented Jan 28, 2015

I think I found it. I click on the Edit menu to open it, click again to close it without choosing anything. CTRL+X does not work. Click twice again on Edit, CTRL+X is back.

@GKFX

This comment has been minimized.

Show comment
Hide comment
@GKFX

GKFX Jan 28, 2015

Contributor

OK, I think I understand how to fix it. It sounds a little fiddly though so I'll wait until the code is more stable before I do any work.

Contributor

GKFX commented Jan 28, 2015

OK, I think I understand how to fix it. It sounds a little fiddly though so I'll wait until the code is more stable before I do any work.

benfry added a commit that referenced this issue Apr 1, 2015

@benfry benfry changed the title from MenuBar shortcuts getting typed into the editor. to Menu mnemonics (alt-f, etc) getting typed into the editor Apr 1, 2015

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Apr 1, 2015

Member

Fixed for 3.0a6.

Member

benfry commented Apr 1, 2015

Fixed for 3.0a6.

@benfry benfry closed this Apr 1, 2015

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