Actually, I am also interested in the related question of how the
"keyboard commands" (SCI_BACKTAB, SCI_CANCEL, SCI_CHARLEFT et al) are
used.
This is for my Scintilla binding for Objective Caml, and my real issue
is "Does anyone really care about binding NON-keyboard commands to a
key sequence in Scintilla?"
To satisfy both "compile-time type safety" AND "avoiding runtime
crashes" goals, it is quite easy to just only allow the "keyboard
commands" Scintilla function subset to be specified with
SCI_ASSIGNCMDKEY (since I am using an enum-like language facility to
represent the Scintilla function names)...
OTOH, if I must allow the use of any Scintilla function which takes no
parameters (because Scintilla users actually use this feature), then I
need to allow all SCI_* function names at compile-time and build *and
maintain* a table of "valid" zero-parameter functions to check against
at runtime. :(
So, *would* any Scintilla users actually be unhappy if I restricted
SCI_ASSIGNCMDKEY to only take "keyboard commands"? And it would be
most helpful if anyone can give real-world [counter-]examples, rather
than "it would be nice to support any of the zero-parameter commands
just like ScintillaDoc.html says"... :)
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
