Message 1 of 1
Per dwg data storage
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi
We need to maintain a few data items on a per-drawing basis, as global configuration items for our custom entities.
We store the items in an AcDbXrecord. At run time we read the data from the dictionary into a struct member of CDocData.
The program uses/changes the data in the struct and writes it back to the AcDbXrecord as needed.
I wonder if we could dispense with the temporary struct and read/write the data on the fly from the AcDbXrecord.
The data is read often - by worldDraw() of every custom entity.
Is there a time (or other) penalty accessing the data in this way?
TIA
alex
We need to maintain a few data items on a per-drawing basis, as global configuration items for our custom entities.
We store the items in an AcDbXrecord. At run time we read the data from the dictionary into a struct member of CDocData.
The program uses/changes the data in the struct and writes it back to the AcDbXrecord as needed.
I wonder if we could dispense with the temporary struct and read/write the data on the fly from the AcDbXrecord.
The data is read often - by worldDraw() of every custom entity.
Is there a time (or other) penalty accessing the data in this way?
TIA
alex