>The onOpen clip bound to an onOpen event is a good idea in that it provides
>a way to set global variables and arrays that can be used in the other
>clips in the library.
>The problem as I see it is that you can actually open a library without the
>"onopen" event being triggered and that when this happens the end user is
>gunna get confused.
When the Clip Editor has the focus, NoteTab assumes you are editing the
library. It would not be helpful for most users to have Clips automatically
executed under this mode. Supposing your OnOpen Clip has a bad bug that
needs fixing. Wouldn't you hate it to be triggered when you have the Clip
editor open, ready to work on it?
>According to the help file An event is a system thingy, it should either
>happen or not .
>When an onopen "event" occurs the "onopen" clip should be there doing it's
Correct, but the event is overridden if the library is open for editing.
You can always execute the OnOpen Clip manually once you close the editor
or move to another document.
NoteTab v4.6a available from
NoteTab v4.8 Beta from