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

Measure Sync with Central duration #9

Open
andydandy74 opened this issue Nov 24, 2017 · 1 comment
Open

Measure Sync with Central duration #9

andydandy74 opened this issue Nov 24, 2017 · 1 comment
Assignees
Labels

Comments

@andydandy74
Copy link
Owner

andydandy74 commented Nov 24, 2017

This data should be delivered as two LoadedModelEvents : Sync_Start and Sync_End - therefore related to #7

Sync start
Option 1 - Sync with settings

Jrn.PushButton "Modal , Synchronize with Central , Dialog_Revit_PartitionsSaveToMaster" , "OK, IDOK"

)
This one has a JournalTimeStamp in the next line where JournalTimeStamp.Description == "ADialog::doModal stop"

or:
Option 2 - Quick sync

Jrn.Command "Ribbon" , "Save the active project back to the Central Model , ID_FILE_SAVE_TO_MASTER_SHORTCUT"

This one has a JournalTimeStamp without a description in the previous line.

Similar events for keyboard shortcuts still need to be recorded.

Sync end
Look for the next JournalTimeStamp where JournalTimeStamp.Description == "idle0_doc"

andydandy74 pushed a commit that referenced this issue Nov 26, 2017
andydandy74 pushed a commit that referenced this issue Dec 15, 2017
@andydandy74 andydandy74 added this to the Pre-Release milestone May 9, 2018
@andydandy74 andydandy74 self-assigned this Nov 30, 2018
@andydandy74 andydandy74 modified the milestones: Pre-Release, Post-Release Dec 4, 2018
@andydandy74 andydandy74 added this to To do in Backlog Dec 4, 2018
@andydandy74 andydandy74 removed this from the Post-Release milestone Dec 4, 2018
@andydandy74 andydandy74 removed this from To do in Backlog Dec 27, 2018
@andydandy74
Copy link
Owner Author

This is actually redundant. It's far easier to pull that data from the worksharing logs. It makes no sense at all to invest an time in this. That node should be removed.

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

No branches or pull requests

1 participant