IBasic |
2025-01-24: This method does not do anything at this time.
The IDE shows the Handlers in the object/proc drop down lists.Use "modulepath|prefix" to create module specific Handlers. If modulepath is a null string, FileName is used. (The string "|..." is the same as prefixing the string with FileName.) An individual Handler in the collection can be accessed using the normal collection index operator.
If prefix begins with "{type}", where type is the name of the language extension type, create handlers for the type's source interface. For example:
{Word.Application}app_
Thing_ Changed Changing(Cancel As Boolean)
This method must be called BEFORE the target code is loaded.
Macro/Module Paths
Macro/module paths are typically file paths. However, it is sometimes useful to work with macros/modules that are not stored as files. A macro/module path is of the form:
[*[*]]path[*]
Part | Description |
---|---|
'*' | Paths that being with '*' are non-file system macro/modules. The application provides the methods for reading and writing these files. Paths that begin and end with '*' are hidden from the IDE. User's can't step into or otherwise inspect the contents. |
'**' | Paths that begin with '**' are non-file system modules. The application provides the methods for reading and writing these files. Running an event-driven module loads it using LoadModule. |
path | This is the identity of the macro/module. |