Class to pass to interface object dump out methods for particular behavior. More...
Inheritance diagram for LaxInterfaces::DumpContext:
Public Member Functions | |
| DumpContext (const char *b, char s) | |
 Public Member Functions inherited from Laxkit::anObject | |
| anObject () | |
| Set object_id=getUniqueNumber(). | |
| virtual | ~anObject () |
| Empty virtual destructor. | |
| virtual const char * | whattype () |
| Returns the type of anObject. | |
| virtual anObject * | duplicate (anObject *ref=NULL) |
| virtual int | inc_count () |
| Increment the data's count by 1. Returns count. | |
| virtual int | dec_count () |
| Decrement the count of the data, deleting if count is less than or equal to 0. | |
| virtual int | the_count () |
Public Attributes | |
| char * | basedir |
| char | subs_only |
| Public Attributes inherited from Laxkit::anObject | |
| int | suppress_debug |
| DeleteRefCountedFunc | deleteMe |
| Called when the count is decremented to 0. | |
| unsigned long | object_id |
| char * | object_idstr |
Additional Inherited Members | |
| Protected Attributes inherited from Laxkit::anObject | |
| int | _count |
| The reference count of the object. | |
Detailed Description
Class to pass to interface object dump out methods for particular behavior.
If basedir!=NULL and saving is happening, then paths saved are relative to basedir. If subs_only==0, then the saved path is always relative to basedir. If subs_only!=0, then the saved path is relative to basedir ONLY if it is in basedir or a subdirectory of basedir. This makes managing project directories a little easier.
If basedir!=NUL and loading is happening, then any relative paths encountered are considered relative to basedir, or the current directory is basedir==NULL. subs_only is ignored when loading.
The documentation for this class was generated from the following files:
- dumpcontext.h
- dumpcontext.cc