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

Improve Journal.LoadedModels #7

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

Improve Journal.LoadedModels #7

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

Comments

@andydandy74
Copy link
Owner

andydandy74 commented Nov 24, 2017

If we want to track all documents opened in a session, we'll need a list of all possible cases and how they can be identified in a journal

Open from Startup Page:

Jrn.Command "StartupPage" , "Dieses Projekt öffnen , ID_FILE_MRU_FILE2"
Jrn.Data "MRUFileName" , "THE_PATH"

Open from Ribbon (CommndID varies depending on selected option):

Jrn.Command "Ribbon" , "Öffnet ein Projekt , ID_REVIT_FILE_OPEN"
Jrn.Data "File Name" , "IDOK", "THE_PATH"

Open by drag and drop:

Jrn.DropFiles MainWnd , ""
Jrn.Data "Dropped File Name" , "THE_PATH"

All of the above done for project files, but need to test if all of the above work for family files as well.
Will also need to investigate how to deal with file names of new local models, currently we're using the central file name. Maybe it's not a bad idea to keep it that way, since we can then track interactions with the central model for multiple users.

Edit Family:

Jrn.Command "Internal" , "Bearbeitet die Familie , ID_EDIT_FAMILY"
Jrn.Directive "DocSymbol" , "[THE_FAMILY_NAME]"

Need to investigate for the following cases:

  • New project/family (from startup page & ribbon)
  • Save As during session
  • New local
  • API background open

Once this is done, move the code to the journal class.

We'll also want to have a LoadedModelEvent for closing a model.

@andydandy74 andydandy74 changed the title Tracking opened documents Improve Journal.LoadedModels Nov 24, 2017
andydandy74 pushed a commit that referenced this issue Dec 13, 2017
@andydandy74 andydandy74 added this to the Pre-Release milestone May 9, 2018
@andydandy74
Copy link
Owner Author

This node is actually painfully slow. Need to investigate what's causing that.

@andydandy74 andydandy74 self-assigned this Nov 30, 2018
@andydandy74 andydandy74 modified the milestones: Pre-Release, Post-Release Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

1 participant