classDLLPlugin 04
e>
| Definition at line 58 of file DLLPlugi.h. References TRUE. | 
| 
 | ||||||||||||||||||||
| When a user clicks within the property control you will receive a call to your virtual OnPtrMessage function. If anyone ever deletes the hgroup, the hgroup will notify all of its dependences (classes that called ReassignPtr with it as a parameter) that hgroup is being deleted. It does this through the OnPtrMessage virtual function in your DllPlugin class. So lets say the user deletes the hgroup in the interface that your plugin has a pointer to. Your DLLPlugin class will receive an OnPtrMessage call that will notify you that the group was deleted. 
 
 Definition at line 63 of file DLLPlugi.h. References FALSE. | 
| 
 | ||||||||||||
| Reading saved values back in is the job of ParseArg. ParseArg is called for each line within the plugin parameters portion of a material file that the standard parser does not understand. This gives you the chance to handle the loading of this data. If you did parse the label, and decide it is one of yours, you should return TRUE, otherwise return FALSE. Here is an example of how to read what we wrote out in the previous example: 
 Definition at line 57 of file DLLPlugi.h. References FALSE. | 
| 
 | ||||||||||||
| ReassignPtr adds information to the assigned object that states that your class has a pointer to it. This information may be used later through calls to OnPtrMessage to let the plugin know that something have happened to the referenced object. Lets say you have this member variable in your CustumTexture class: You can call This will set m_mygroup to hgroup. You do this rather than m_mygroup = group. What ReassignPtr actually does is adds information to the hgroup that states that your class has a pointer to it. 
 
 
 Definition at line 62 of file DLLPlugi.h. References m_treeobject, and HTreeObject::ReassignPtr(). Here is the call graph for this function: | 
| 
 | ||||||||||||||||
| When a plugin specific parameter set is saved to disk, the Save function is called to write out your custom data. Some common examples of things written in this function are boolean variables, and filenames. Save is continuously called until you return FALSE. The count variable starts out at zero on the first call, and increments for each subsequent call. For each item you wish to write you fill the label and value variables with the appropriate text. For example: This would write a line out in the material file that says "ShowPreview=ON". You would add more cases for each line you wish to write out. Labels should be choosen so that they are not mistaken with any typical reserved labels in the A:M files. See CustomTexture::ParseArg for an explanation. 
 
 Definition at line 56 of file DLLPlugi.h. References FALSE. |