search

Jaeyo / lanterna

Automatically exported from code.google.com/p/lanterna
GNU Lesser General Public License v3.0
0 stars 0 forks source link

F1 to F5 keys are not working on xterm and vt220 terminal #115

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
F1 to F5 keys are being sent as OP,OQ,OR and OS on xterm and vt220 terminals. I 
have tried this with version 2.1.7 and 2.1.8.

Original issue reported on code.google.com by venu1...@gmail.com on 14 Aug 2014 at 6:28

GoogleCodeExporter commented 9 years ago 
Yes, there is a limitation in the input decoder which makes these accidentally 
show up as ALT + O and then P, Q, R or S. Before I got started on 3.0, I 
actually began to re-write the input decoder, you can enable this experimental 
code by setting system property 
com.googlecode.lanterna.input.enable-new-decoder to "true". It's pretty 
untested though.

This problem has been fixed in 3.0, which should be ready unless you use the 
GUI layer.

Original comment by mab...@gmail.com on 21 Aug 2014 at 12:24

GoogleCodeExporter commented 9 years ago 
Yes, there is a limitation in the input decoder which makes these accidentally 
show up as ALT + O and then P, Q, R or S. Before I got started on 3.0, I 
actually began to re-write the input decoder, you can enable this experimental 
code by setting system property 
com.googlecode.lanterna.input.enable-new-decoder to "true". It's pretty 
untested though.

This problem has been fixed in 3.0, which should be ready unless you use the 
GUI layer.

Original comment by mab...@gmail.com on 21 Aug 2014 at 12:24

GoogleCodeExporter commented 9 years ago 
I have tried by setting com.googlecode.lanterna.input.enable-new-decoder to 
true but It didn't work.

I am using the GUI layer. Is there anyway I can port the fix back to 2.1.8 ? I 
have a business case where I have to use the F4 key. Appreciate your help!

Original comment by venu1...@gmail.com on 26 Aug 2014 at 3:26

GoogleCodeExporter commented 9 years ago 
Okay, I've added a hack in the old input decoder that recognizes F1-F4. Try the 
latest release/2.1 branch and set system property 
"com.googlecode.lanterna.input.function_key_hack" to "true" to activate this.

Original comment by mab...@gmail.com on 21 Sep 2014 at 2:08

GoogleCodeExporter commented 9 years ago 
Is it possible to get the source code for this 2.1 branch ? I have done some 
modifications to 2.1.8 version for my application so I have to keep those 
changes well. Thanks for your help.

Original comment by venu1...@gmail.com on 21 Sep 2014 at 2:45

GoogleCodeExporter commented 9 years ago 
The branch is available in the usual Git repository.

Original comment by mab...@gmail.com on 21 Sep 2014 at 11:37

GoogleCodeExporter commented 9 years ago 
I tried this with 2.1 branch and it's still not working for me. I did set 
system property "com.googlecode.lanterna.input.function_key_hack" to true.

Original comment by venu1...@gmail.com on 14 Oct 2014 at 5:35

GoogleCodeExporter commented 9 years ago 
Yes, I now see why, I never pushed the change! Please try again; pull latest 
changes, recompile 2.1 branch and set the property to true.

Original comment by mab...@gmail.com on 19 Oct 2014 at 6:32

GoogleCodeExporter commented 9 years ago 
It's working now. Thank you so much.

Original comment by venu1...@gmail.com on 21 Oct 2014 at 3:57