David Flanagan wrote: > Hussein Shafie wrote: > >> Sorry to disappoint you and to have made you loose your time. XXE V2.x >> is *not* flexible enough to allow you to do what you want. >> >> To make it simple, you can define and install your own bindings once >> the document is openened. You cannot define and install bindings to >> open a document. >> > > So bindings defined in customize.xxe are not used directly, but are > applied to each document when it is opened?
The bindings found in customize.xxe do not customize the application, they customize the document views. Let's suppose you have successfully bound "Ctrl-X Ctrl-F" to command "XXE.open". For "Ctrl-X Ctrl-F" to do something, you must: 1) Have at least one document view opened. That is, it will not work if no documents are opened in XXE.(Because it is the document view, not the application, which triggers a command.) 2) The document view must not be iconified and must have the keyboard focus. This means that binding "Ctrl-X Ctrl-F" to command "XXE.open" would not be very useful. What you really want to do is redefine the menu accelerator of File|Open and this is not possible with XXE V2.x. >> XXE.open, XXE.save, etc, are currently only used to write macro-commands. >> > > If I write a macro that just calls XXE.open, can I then bind that macro > to a keystroke? That's not what I meant. A creative use of XXE.open in a macro is, for example, to generate a modified version of the document being edited using a process command and then to load the modified version in XXE. Now, having said this, you are right because, for obscure implementation reasons, if you write a macro that just calls XXE.open, then you can bind that macro to a keystroke. Hum, this looks like a bug... If you can do this using a trivial macro, you should be able to do it without a macro. We'll try to fix this bug in next release.
