Using the qt plugin is now possible, but is annoying because of small omissions and differences from how Leo normally works. The to-do list contains most of the annoyances. Here are the first entries:
Ask Qt people: - How to enable accelerators. - How to add an accelerator to file yes,no,cancel dialog, so I can type 'n'. - Is it possible to specify QScintilla styles with a stylesheet? Urgent: - Call setLexer(0) for nocolor nodes. ** Cut and paste should use native widget code - Ctrl-k loses scroll position ** In minibuffer "#" yields "numbersign", '_' yields underscore, '-' yields minus. - Alt-1, Alt-2 bindings do not work * Tab and space handling are subtly different from traditional Leo way. - Reading/saving a window does not properly set its size. - Can not open the settings file twice. Not on the list, but a real possibility, is using another kind of Qt widget for the body pane. This might allow easier configuration with stylesheets, and more importantly, would support Leo's notion of character indices, which would allow Leo's commands (and the threading_colorizer) to "just work". Long term, QScintilla is probably the way to go, but short term we need a workaround to the QScintilla character-index problems. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
