Normal
In my quest I decided to dig deeper into MP2. As I was going through I came across IWorkflowModel.cs and noticed a small TODO: // TODO: Create methods Activate and Deactivate to execute initialization/deinitialization like message queue setup etc. // EnterModelContext and ExitModelContext can then be replaced by ChangeModelContext. While I didn't implement ChangeModelContext I did add an void Activate(NavigationContext currentContext); function to IWorkflowModel.cs and implemented it in WorkflowManager.cs at the end of the function UpdateScreen_NeedsLock(bool push, bool force) After that I found I was able to get my dialog to appear but while the thread is working on the first load of the form the side menu expands until the dialog is shown. At the moment I'm not sure what's causing the menu to expand in the first place but it's causing me grief. So I guess the follow up question is how did @Albert I guess intend the Activate function to work so I can do this properly?
In my quest I decided to dig deeper into MP2. As I was going through I came across IWorkflowModel.cs and noticed a small TODO:
// TODO: Create methods Activate and Deactivate to execute initialization/deinitialization like message queue setup etc.
// EnterModelContext and ExitModelContext can then be replaced by ChangeModelContext.
While I didn't implement ChangeModelContext I did add an void Activate(NavigationContext currentContext); function to IWorkflowModel.cs and implemented it in WorkflowManager.cs at the end of the function UpdateScreen_NeedsLock(bool push, bool force)
After that I found I was able to get my dialog to appear but while the thread is working on the first load of the form the side menu expands until the dialog is shown.
At the moment I'm not sure what's causing the menu to expand in the first place but it's causing me grief.
So I guess the follow up question is how did @Albert I guess intend the Activate function to work so I can do this properly?