I’ve noticed the following behavior.
If after starting Rhino a User creates a new document or opens an existing one, Rhino fires two undo events.
IsBeforeBeginRecordingBeginRecording
It then proceeds to ask the user to select a template/file. If the user cancels, we get the expected events to undo changes made in a cancelled command:
IsBeforeEndRecordingEndRecordingIsPurgeRecord
However if the user clicks through and creates/opens a document, we don’t get the IsBeforeEndRecording or EndRecording event.
It’s something that can be accounted for by watching for the close document event, which only happens if the user doesn’t cancel the action. But it feels different from every other time Rhino indicates that it’s starting to record, which is that we get the events telling us that it’s done recording.
The simplest way to for me to handle this is to make the assumption that if I see a document close event to assume that we’ve done with recording anything related to the document. Please let me know you see any potential issues with treating the document close event as a proxy for the IsBeforeEndRecording and EndRecording events.
Thanks,
Cullen