samskivert
commented
9 years ago Interesting! JavaFX (which is the UI toolkit on which Scaled is built) is woefully limited in how it allows me to interact with the keyboard, but hopefully I can figure out some way to extract the right information from its key events.
I'm guessing that when it reports a key pressed event (which has the logical keycodes), it reports K (the Qwerty key) even though you pressed E (in your Colemak layout), and only when the key typed event comes in, does it report a character code of 'e'.
Or it might have to do with the fact that the CTRL key is held down. JavaFX seems to arbitrarily decide whether to provide "keymap translated" information depending on which modifier keys are down. It does different things if SHIFT is down, or if CTRL is down, or if META is down. And there are weird bugs where it generates spurious keyboard events in some circumstances. I have an outstanding bug that's been bouncing between JDK/JavaFX engineers for six months now: https://javafx-jira.kenai.com/browse/RT-37399
Anyway, that bug report has a program in it:
import java.util.Arrays;
import java.util.Set;
import java.util.HashSet;
import javafx.application.Application;
import javafx.event.ActionEvent;
import javafx.event.EventHandler;
import javafx.scene.Scene;
import javafx.scene.input.KeyEvent;
import javafx.scene.control.Label;
import javafx.scene.layout.StackPane;
import javafx.stage.Stage;
public class MetaDot extends Application {
public static void main(String[] args) {
launch(args);
}
@Override
public void start(Stage primaryStage) {
primaryStage.setTitle("Meta Dot!");
StackPane root = new StackPane();
root.getChildren().add(new Label("Press Meta Dot."));
primaryStage.addEventHandler(KeyEvent.ANY, ev -> System.out.println(toDebugString(ev)));
primaryStage.setScene(new Scene(root, 300, 250));
primaryStage.show();
}
private String toDebugString (KeyEvent ev) {
StringBuilder sb = new StringBuilder();
sb.append("type=").append(ev.getEventType());
sb.append(" code=").append(ev.getCode());
sb.append(" mods=").append(getModifiers(ev));
sb.append(" char='").append(ev.getCharacter());
sb.append("' (");
for (char c : ev.getCharacter().toCharArray()) sb.append(" ").append((int)c);
sb.append(")");
return sb.toString();
}
private Set<String> getModifiers (KeyEvent ev) {
Set<String> set = new HashSet<>();
if (ev.isAltDown()) set.add("alt");
if (ev.isControlDown()) set.add("ctrl");
if (ev.isMetaDown()) set.add("meta");
if (ev.isShiftDown()) set.add("shift");
return set;
}
}If you could compile that program, and press CTRL-e and send me the output, that'd give me a better idea of what events JavaFX is generating and what I might need to do to work around its foolishness.
Eventually, I'm probably going to have to write native code to handle key input because the JavaFX team seems not to know what they're doing much in that regard. But I'd like to avoid that substantial complication to Scaled's build and deployment as long as I can.
xpe
iphydf
I use the Colemak layout. When I type normal characters into Scaled, they appear correctly. However, commands such as "C-e" are not interpreted correctly. Perhaps there are some low-level options you can check on?
(For example, the "k" key in Qwerty corresponds to the "e" key in Colemak, for example. So when I press "C-e" Scaled deletes the line.)