I'm using a InclineCssTextArea as a basic field, but the problem is the new line functionality doesn't seem customizable. I know I can just use TextField, but one of the reasons why I chose RichTextFX is because it can handle special characters like heart symbols automatically if the font doesn't have them by default. So I don't have any choice but to use your text areas.

To summarize, how do I prevent being able to press enter and start a new line on a text area like this? It needs to remain in one line forever. I already have setWrapText(false) on the area.
I saw this, but I was wondering if any progress had been made on it, or if you guys can make a workaround. I really need the special character handling of RichTextFX, so there's not an alternative for me unless I remove that functionality, which is very bad because my software is for video games, which tend to need those characters for creative reasons. I'm okay with something like overriding the button listener to disable it, or something equally hacky like that for now until you guys make a proper system for it.
Thanks!
I'm using a InclineCssTextArea as a basic field, but the problem is the new line functionality doesn't seem customizable. I know I can just use TextField, but one of the reasons why I chose RichTextFX is because it can handle special characters like heart symbols automatically if the font doesn't have them by default. So I don't have any choice but to use your text areas.
To summarize, how do I prevent being able to press enter and start a new line on a text area like this? It needs to remain in one line forever. I already have setWrapText(false) on the area.
I saw this, but I was wondering if any progress had been made on it, or if you guys can make a workaround. I really need the special character handling of RichTextFX, so there's not an alternative for me unless I remove that functionality, which is very bad because my software is for video games, which tend to need those characters for creative reasons. I'm okay with something like overriding the button listener to disable it, or something equally hacky like that for now until you guys make a proper system for it.
Thanks!