Journalysis
Journalysis copied to clipboard
Revit journal and worksharing log analysis package for the Dynamo visual programming environment
Not urgent, but would be nice eventually - [ ] Helpers.AllJournalAPIMessageTypes - [ ] Helpers.AllJournalCommandTypes - [ ] Helpers.AllJournalLineTypes - [ ] Helpers.AllJournalMouseEventTypes - [ ] Helpers.AllJournalSystemInformationTypes - [ ]...
For JournalAPIMessages: * ExceptionType (first word in message) * ExceptionMessage (content of first parentheses) * ExceptionHandler (after "was thrown from a handler of") * Application (after "was registered by application")...
It would make the usage of the startup time more meaningful if we could distinguish between sessions that display a task dialog during startup (e.g. warnings for unsigned addins).
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...
I think these are the only Dynamo related events that can be measured fairly reliably... **Launching Dynamo** ```JournalCommand``` via ribbon: ``` Jrn.Command "Ribbon" , "Launch Dynamo , ID_VISUAL_PROGRAMMING_DYNAMO" ``` ```JournalCommand```...
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...
This kind of line should register as an exception - [x] Add in 2.12.0 - [ ] Migrate to 3.0.0
Add this as a new type in JournalAPIMessage: - [x] Add in 2.12.0 - [ ] Migrate to 3.0.0