next up previous contents
Next: 6.8 Extending PaPCo read Up: 6. Including your own Previous: 6.6 Plot and Read

6.7 Initializing your module

To make sure your module's files are compiled when PaPCo starts up, you need to make an init-file. This file HAS TO BE CALLED YOUR_MODULE_DIR\init_module.pro in order for PaPCo to find it. Each module has it's own init_module.pro file. Here is the example of what the init file for plot_type looks like:

$\textstyle \parbox{\hsize}{\verbatiminput{init_module.pro}}$

As you can see, the init-file is divided into plot- and read-routines, and those that are needed to interface with PaPCo.

Each time PaPCo is started, it searches all the YOUR_MODULE_DIR\init_module.pro files it can find in the IDL search path and writes its own papco_user\papco_add_init.pro file dynamically. A new file is produced each time you start PaPCo, and you can examine it to see whether your modules have been found.

Depending on which modules you plan to add to your PaPCo session, you will need to make changes in the PaPCo configure widget (see Section 3.4). The papco_user\papco_add_init.pro file is automatically produced and updated.

Remember: PaPCo will add a button for all the modules that have their papcoadd_plot_type file in YOUR_MODULE_DIR\papco_interface.


next up previous contents
Next: 6.8 Extending PaPCo read Up: 6. Including your own Previous: 6.6 Plot and Read
Reiner Friedel
1999-02-03