767 2013-06-27 00:28:59 +0200 whitespace key events are classified as 'non printable' 2013-07-03 23:08:28 +0200 1 1 3 JogAmp Newt awt 1 pc_x86_64 windows RESOLVED FIXED --- minor --- 1 msiggy sgothel --- 4c34f5980bddcdc84b10cb3bcbb96b365b9d471e 4e6c2aadd7d652db3ba1f35eef1a3d61d6e692d0 --- oldest_to_newest 2720 0 msiggy 2013-06-27 00:28:59 +0200 KeyEvents fired by whitespace keys such as tab, enter, and backspace are flagged as 'non printable'. In other words they return 'true' for their 'isPrintableKey()' method. 2737 1 sgothel 2013-07-02 16:13:20 +0200 (In reply to comment #0) > KeyEvents fired by whitespace keys such as tab, enter, and backspace are > flagged as 'non printable'. In other words they return 'true' for their > 'isPrintableKey()' method. .. they do not return 'true' for their 'isPrintableKey()' method, but should! 2747 2 sgothel 2013-07-02 18:48:48 +0200 ENTER (currently wrong keyCode 0xa -> 0xd) is not a printable IMHO but more a control sequence. TAB + BS .. well, adding them is a compromise maybe, while understanding the view from a 'editor' perspective not font-definition perspective. 2748 3 sgothel 2013-07-02 19:02:10 +0200 TAB + BS are considered 'printable' - Compromise of 'editor' view and 'font-definition' view. ENTER not. Fix ENTER code: 0xa -> 0xd ! 2763 4 sgothel 2013-07-03 23:08:28 +0200 Revise commit 4c34f5980bddcdc84b10cb3bcbb96b365b9d471e (Bug 767): TAB, BS and CR/ENTER are printable for NEWT KeyEvent and font handling. Fix regression. - Original behavior was treating CR/ENTER them as printable, lets keep it this way. - KeyEvent: Query these 3 whitespaces upfront, no need to incl. them in 'nonPrintableKeys'. - Fix regression: Native VK_ENTER was not change in commit 4c34f5980bddcdc84b10cb3bcbb96b365b9d471e. .. TL;DR .. so it is as you (Mike) suggested. All good!