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

No [ ] { } writable on OS X 10.10.3 in CodeArea #139

Closed
Morvs opened this issue Apr 13, 2015 · 5 comments
Closed

No [ ] { } writable on OS X 10.10.3 in CodeArea #139

Morvs opened this issue Apr 13, 2015 · 5 comments

Comments

@Morvs
Copy link

Morvs commented Apr 13, 2015

Hi,

I was trying to write a code editor with your lib but I can't write brackets or curly braces. I'm using a german layout on a Macbook where brackets are written with ALT + 5/6 and curly braces with ALT + 8/9. To be exact none of the symbols requiring ALT are writable.
I'm not that sure right now but I thought it was working with 10.10.2 as I was testing it some days ago before the third update of 10.10.
I tried both the demos of Java syntax highlighting and using eclipse with this code but I can't write them. Copy pasting them works though.

Also, using Windows 8.1 on the same Macbook running the same demos I am able to write those brackets and curly braces so it seems to be system specific.

If you've got any idea of what's the issue or if I can provide any further information, just let me know.

@TomasMikula
Copy link
Member

Thanks for reporting. Can you try whether they work in a plain JavaFX TextArea?

@Morvs
Copy link
Author

Morvs commented Apr 13, 2015

Just tried it with the code from here -> http://www.java2s.com/Code/Java/JavaFX/UsingTextAreatodisplaymorelines.htm

It works flawlessly with the usual TextArea.

@Morvs
Copy link
Author

Morvs commented Apr 14, 2015

Just a little note: I was on a little bit outdated jdk (8_u25) which i noticed this morning but updating to the current version 8_u40 didn't help either. I also noticed that my project in eclipse was set to use jdk 1.5 but as you may expect, changing to 1.8 sadly didn't help.

@TomasMikula
Copy link
Member

Please, try this with the new 0.6.4 release.

@Morvs
Copy link
Author

Morvs commented Apr 21, 2015

Now it's working (again).

Thank you for solving the issue.

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