| <<< Note 2113.0 by TAEC::HARPER "John Harper, DTN 830 3647" >>>
-< Iconic Map extensibility? >-
I have a couple of questions concerning the modularity and
extensibility of the Iconic Map PM.
1. Suppose I write a simple AM for some new kind of global
entity. Can I, and if so how, add a new icon for it to the
Iconic Map toolbox?
--> This one's an easy one...
Your AM defines a global entity class, say "foo". To add an
Icon, use DECpaint or whatever you want to create an X11 file
and put it in the MCC_ICONS location called
MCC_foo_ICON.DAT
The next time you bring up the iconic map, it will find the new
entity in the dictionary and find the icon in the right place.
2. Suppose I write a new FM providing some "added value" function
such as, for example, the Alarms FM. (That's a pretty extreme
case, but what I'm getting at is something that provides a
new KIND of function).
Can I, and if so how, add a new set of windows to the Iconic Map
to allow me to manipulate my new function?
--> Since you are in Valbonne (or at least using a system in
Valbonne), check with Marc Flauw, we are putting functions in
for PNMP that all can use to have more flexibility in creating
"sub" windows from the Iconic Map.
Thanks,
John
|
| >--> This one's an easy one...
> Your AM defines a global entity class, say "foo". To add an
> Icon, use DECpaint or whatever you want to create an X11 file
> and put it in the MCC_ICONS location called
> MCC_foo_ICON.DAT
> The next time you bring up the iconic map, it will find the new
> entity in the dictionary and find the icon in the right place.
I found there to be some code number dependency here. The first time
I tried it, I defined my global entity with type code 88 (the one
from the design framework) and this did not work. I just changed the
code to 15 (Sample's) and it worked fine. (I'm using EFT 1.2 BL15.)
In general, I've had a bit of trouble with the private codes,
although I haven't been through the entire mountain of documentation
yet. The MM Programming document says there are private codes and
that they are defined in mcc_ve?_def.h but there are no comments in
the header file and I'm not sure what the private codes are or how
they are intended to be used.
Is there a rule of thumb I can use for defining global entities and
types? Something like "all codes between 16K and 32K are reserved
for development" would be nice.
- John
|