[vwnc] Code editing feels vs ParagraphEditor

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] Code editing feels vs ParagraphEditor

Randy Coulman
This is something we got burned by a while ago, and I probably complained about it then, but we just got burned again, so I'm complaining again....

ParagraphEditor>>initialize turns on code editing feels by default.  In our application, we take pains to turn those off for the few paragraph editors we have in our application (now that we know what the problem is). 

Why does ParagraphEditor default these to true?  I can't think of any good reason for it.  They should be off by default, and only enabled when they're really wanted.

(Background)
Our systems are normally touch-screen only, but it is possible to plug in a USB keyboard when necessary.  The keyboards we ship with our systems have a set of programmable function keys across the top (which we don't use, so don't configure).  Either when plugging in the keyboard, or if those function keys get pressed, we get certain (random? not sure yet) characters sent to our application.

The logs we saw today showed that a Ctrl-L was sent (opening the Find dialog), followed by a Ctrl-E, which attempted to do an "explain"; however, in a base image, the support for explain seems to be stripped out.  Thus, we got a UHE because the find dialog has a ParagraphEditor that we don't control, and therefore don't disable code editing feels on.

Randy
--
Randy Coulman
[hidden email]

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc