It appears the API call to Bentley.MstnPlatformNET.WinForms.Apapter.AttachAsTopLevelForm was broken somewhere between ORD 10.09.0.91 (MS 10.14.04.04) and ORD 10.10.21.04 (MS 10.16.02.267) . Forms no longer minimize or stay in front of the main ustn window as in previous versions.
Has anyone else encountered this issue?
Hi Mike Robertson,
Couple quick questions.
I tried this in MSCE 10.16.2.22 and do not see any problem using the WpfDemo's: Minimize (Alt + Tab restores), Docking or Open Modal tests - and do not see any other window ordering issues present.
Thank you,Bob
I installed and tested with ORD 10.10.21.04 and do not see any difference in behavior in the WpfDemo example. I am also running Windows 10 most current patches:
HTH,Bob
Our WPF based forms (and the WpdDemo) work correctly. These are forms based off of public partial class FormPlaceBoreInPlan : Bentley.MstnPlatformNET.WinForms.Adapter.
//form definition and iheritance #if RELEASE public partial class FormPlaceBoreInModel : Bentley.MstnPlatformNET.WinForms.Adapter #else public partial class FormPlaceBoreInModel : Form #endif //form creation and show FormPlaceBoreInModel formPlaceBoreInModel = new FormPlaceBoreInModel(); #if RELEASE formPlaceBoreInModel.AttachAsTopLevelForm(ORDPlaceBorehole.Instance, true); #endif formPlaceBoreInModel.Show();
Mike Robertson said:It appears the API call to Bentley.MstnPlatformNET.WinForms.Apapter.AttachAsTopLevelForm was broken
Mike Robertson said:Our WPF based forms (and the WpdDemo) work correctly. These are forms based off of public partial class FormPlaceBoreInPlan : Bentley.MstnPlatformNET.WinForms.Adapter
Just to be clear, is your problem with Microsoft WinForms or with WPF?
Your AddIn UI class should inherit from the appropriate Bentley base class. If you're using WinForms, this is OK...
#if RELEASE public partial class FormPlaceBoreInModel : Bentley.MstnPlatformNET.WinForms.Adapter #else public partial class FormPlaceBoreInModel : Form #endif
But if using WPF, the above makes no sense.
Regards, Jon Summers LA Solutions
Yes, our Winforms based forms (Bentley.MstnPlatformNET.WinForms.Adapter) are the ones displaying this incorrect behavior, our WPF forms are behaving correctly.
Well, I feel like an idiot, got caught in a situation of side by side ORD installations. My debug was building to ORD10.10 addin locatio,n but my release was still building to ORD10.09 location. So I was not launching a release version (with the AttachAsTopLevelForm implementation).
Answer Verified By: Mike Robertson