Printing - FoxTalk - dFPUG-Portal

Passing the name of a registered add-in to the DoAddIn() method will run that add-in.
You can also call the add-in with the add-in button. Clicking on the add-in button activates a
menu with the installed add-ins. The same menu can be expanded manually with the
AddInMenu() method as follows:
_oBrowser.AddInMenu()
Running this method will expand the menu at the location of the mouse pointer. You can close
the menu with _oBrowser.DeactivateMenu(), although you shouldn't need to because the menu is
automatically closed when a selection is made.
Unregistering an add-in
You can also remove an add-in from the Browser Registration table with the AddIn() method:
_oBrowser.AddIn("Class Name",.NULL.)
If the program name is provided as a value of .NULL., the add-in record in the browser
registration table is marked for deletion.
Creating custom add-ins
Add-ins let you control many events and extend or override existing behavior. The previous
example is a trivial one that simply displays the name of the currently selected class. It
accomplishes this by accepting the object parameter (remember, the Class Browser form object
is the parameter) and then accessing the Class Browser's cClass property in the WAIT
WINDOW command.
While this example isn't particularly useful, it does illustrate a few key concepts. First, by
sending itself as the parameter to the add-ins, every add-in has access to the full power of the
Class Browser. That's why it's so important to take the time to learn about the objects, properties,
events, and methods of the Class Browser (they're all documented in the Visual FoxPro help
file). Another key point here is that there isn't much that an add-in can't do for you.
Here's another example of an add-in: This one inserts additional header information to the code
exported with the Class Browser's ExportClass() method. It's useful when you have to represent
a class in code. You may need to do this for system documentation, when writing articles or
books, and so forth: