Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCD format enhancements #2148

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

lpechacek
Copy link
Member

This patch set is related to various OCD format support enhancements. The first two commits complement existing changes in the repo. The next two add new functionality for the sake of compatibility. I'd be happy if they were merged into the mainline Mapper code.

The dominant color id is stored both in the index entry and the main
object struct.

Amends commit 6d5d317 (OcdFileExport: Set color in object index
entry).
The export routines store the "show at least one gap" line symbol
property as the OCD minimum number of gaps/symbols. This commit
complements the export path code and implements translation from the
number of gaps/symbols to the Mapper symbol property.

Amends commit 908d404 (Implement export to .ocd version 8).
Starting from v12 format the object features fields for creation and
modification times. Some users use the modification time to identify
changed objects. Mapper can support this workflow by maintaining the
creation and modification times on the map objects. This patch does not
implement object timestamp updates in Mapper.

The conversion of the floating point number to date and time is
described at
https://docwiki.embarcadero.com/Libraries/Alexandria/en/System.TDateTime
Examination of real OCD files has revealed that the server object id is
customarily filled with -1.
@dl3sdo
Copy link
Member

dl3sdo commented Apr 12, 2023

Libor, thank you for the PR.
I am happy to see that you started to address the topic of object timestamps which I really want to have in Mapper for a number of reasons.
Thus I would prefer to go even one step further and not add the timestamps to the objects' tags but instead as object properties and also save them in omap file format directly.
This would not imply that the full support of timestamp updates needs to be provided immediately.

@lpechacek
Copy link
Member Author

Thanks, Matthias, for the review! I'm not against addition of the timestamps as an object property and I can implement it if the feature is aligned with the project roadmap.

Copy link
Member

@dl3sdo dl3sdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the value should be set to -1 as my analysis of .ocd12 files shows as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants