--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>
+<classpath>
+ <classpathentry kind="src" path="src"/>
+ <classpathentry exported="true" kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
+ <classpathentry kind="output" path="bin"/>
+</classpath>
*.class
+bin/**
+build/**
# Mobile Tools for Java (J2ME)
.mtj.tmp/
# Scratch space
misc/**
+/.project~
--- /dev/null
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>jexer</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.jdt.core.javabuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.jdt.core.javanature</nature>
+ </natures>
+</projectDescription>
input (see the ENABLE_LINE_INPUT flag for GetConsoleMode() and
SetConsoleMode()).
+ ECMA48 Backend
+ --------------
+
+ - Mouse support for BackendType.ECMA48/XTERM currently requires UTF-8
+ coordinates (1005 mode). Terminals that support UTF-8 mouse coordinates
+ include xterm, rxvt-unicode, gnome-terminal, and konsole. Due to Java's
+ InputStreamReader requirement of a valid UTF-8 stream, one must assume
+ the terminal will always generate correct UTF-8 bytes. Mode 1006 (SGR)
+ will be supported in a future release.
+
Roadmap
0.0.5: BUG HUNT
- TSubMenu keyboard mnemonic not working
+- ECMA48Terminal
+ - Mode 1006 mouse coordinates
0.1.0: BETA RELEASE
-->
-<project name="jexer" basedir="." default="run">
+<project name="jexer" basedir="." default="jar">
<property name="src.dir" value="src"/>
<property name="resources.dir" value="resources"/>
import java.util.List;
import java.util.LinkedList;
-import jexer.TKeypress;
import jexer.bits.Color;
import jexer.event.TInputEvent;
import jexer.event.TKeypressEvent;
*/
private Object listener;
- /**
- * When true, the terminal is sending non-UTF8 bytes when reporting mouse
- * events.
- *
- * TODO: Add broken mouse detection back into the reader.
- */
- private boolean brokenTerminalUTFMouse = false;
-
/**
* Get the output writer.
*