Monday, May 26, 2008, 11:08:32 AM, Jean Jordaan wrote: > Hi there > >> Sorry but we have chosen not to interfere with the standard Java/Swing >> keyboard bindings > > Usually I'd agree with that as principle, but in this case I can only > regard the standard bindings as primitives without reference to > particular usage. They're definitely broken as far as usage in a text > editor is concerned.
Looking at Hussein's answer again, I feel I have to re-explain my report. The problem with XXE is with the way it moves the *caret* when I press Page Down or Ctrl + End. The scroll bar moves are OK (I hope...). Most certainly Swing doesn't specify how to move the *caret*, especially not within a custom editor component... but then I'm barely write GUI stuff. It would be shocking if it specifies that, but in this odd way as it works now in XXE. <OT> The other thing is, I find this "it's their mistake" approach strange. Swing applications always had quite annoying and childish issues, as far as I can remember whenever used them... no wonder IBM rather pushes its own GUI library (SWT). Surely this is all Sun's mistake, but the end-user doesn't care (or understand) whose mistake is what... He just buys a GUI application, and if it has glitches, then that will be a reputation/money loss for the company who sells the application. That said, if I were XMLmind, I would certainly look for workarounds. Like, here is the utterly annoying Swing bug, that they have once fixed but then re-introduced it seems, where Alt + Tab will randomly focus the menu. Or, that Ctrl + Insert and Shift + Insert doesn't work on Windows, where it's a standard binding for copy/paste. And no, customization is not an answer... I'm talking about the out-of-the-box behavior. </OT> -- Best regards, Daniel Dekany
