← All bug reports

FS#2488Not saved/loaded custom properties when the title is not 'QCAD' and unlisted in Property Editor.

Type
Feature Request
Status
Closed
Resolution
Won't implement
Category
QCAD (main)
Severity
Low
Priority
Low
Reported version
3.28.1
Operating system
All
Reported
2023-08-18 by CVH
Closed
2023-08-18 by andrew
Votes
1

Andrew,

Discovered in writing a custom tool:
hatchEntity.setCustomProperty("MijnEPB", "Ruimte", roomData.numberText);
Works perfectly and I can retrieve the room numbers of all semi-automatically placed hatches in this instance of QCAD.

But I can not store and reload this file with these custom properties to use them in a new QCAD session.
I then assume the title must be 'QCAD'.
Then I wonder how QCAD handles custom properties by other CAD applications.
Are they also removed on loading/writing?

QCAD doesn't list these custom properties in the Property Editor.
Here hidden was fine unless they are not stored with the document.

Is it even possible to store them in the drawing file?
Why is the title a required variable when it can't differ from 'QCAD'?
Would it be possible to list them up in the Property Editor because I know they are filtered on title 'QCAD'.

For now I revert to:
hatchEntity.setCustomProperty("QCAD", "EPB-Ruimte", roomData.numberText);
Similar as the CAM tool that uses 'Cam....' for all keys.

Regards,
CVH

Comments (1)

andrew 2023-08-18

QCAD stores properties always as string type in the format "key:value" while other applications store properties as different types with DXF style number keys.

When loading a file, QCAD needs to know for sure if a property is stored in QCAD "key:value" format or in another format. That's the reason why the app needs to be "QCAD" when a document is saved to DXF/DWG.

The AppID can have other uses for other formats / applications in other plugins.

Closure comment

AppID has to be "QCAD" for DXF/DWG.