Hello,
we have a problem, in Microstation Connect, when we load our programs (ma), these are then saved in the upf, and MicroStation reloads them automatically the next time the plan is opened.
We do not want this behavior.
We tried to unload them in the callback function SystemCallback::SetExitDesignFileStateFunction, but it's too late, it's already saved in the upf.
we also tried SetDgnFileUnloadingFunction, but this callback does not work.
Is there a method for not having our programs register in the upf file?
Rgds,
Goubier Sébastien
Sebastien GOUBIER said:MicroStation reloads them automatically the next time the plan is opened
Here's a post about something similar when using a customised toolbox in CONNECT. In this case, MicroStation prevents the app from unloading because the custom toolbox holds on to the apps's .ma file.
.ma
Regards, Jon Summers LA Solutions
in my case, no customised toolbox.Only my ma, and my dll with their own interfaces.
I try to close all the interface on SetExitDesignFileStateFunction but without succes.
At the moment I have no solution
Sébastien
Ahhh, it's ok now !
I used an asynchronous function to close the toolbox.
Now I use : G_dlgTools->Close(true, HideReasonCode::MdlUnload, true); and it's ok !!
Perfect
Sebastien GOUBIER said:I used an asynchronous function to close the toolbox.
Oops, not good solution when it's necessary to wait for the closing finish ;-)
Sebastien GOUBIER said:and it's ok !!
Good to know it works now!
... and also that the problem is still the same (opened toolboxes are remembered).
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Sebastien GOUBIER,
Do you mind letting us know (per our Community posting Best Practices) what exact version of MicroStation you are seeing this issue in?
Artur Goldsweer and I noticed autoload of MDL toolboxes behavior may have been corrected in code (outside of) Defect 437059, so I cannot confirm with 100% certainty if it is corrected (with clean installs) or a different path/behavior may not have been addressed.
If you are running a (clean install) of MicroStation CONNECT U14 and SDK w/recompiled app and still seeing the behavior described above could you reply (when convenient) with a simplified test case so we can confirm under clean software installs a new defect or elevating the existing defect is required?
Thank you in advance,Bob
Hi Robert,We had this problem of autoload MDL in the version U13 with SDK13 and also in the version U14 SDK14. [CONNECT U14 C++]
I did not understand, you want me to confirm that under Micostation Connect U14 the problem is still present with a simple case?
Or do you want a code snippet?
How edit the subjet ?
Hi
Sebastien GOUBIER said:you want me to confirm that under Micostation Connect U14 the problem is still present
Yes please, since I believe we may not see this behavior, but your code may be doing something unique above and beyond the delivered MyApp example we used to confirm no longer seeing the autoload behavior when running in U14.
Sebastien GOUBIER said:problem is still present with a simple case?
If you still see the problem in U14 (commenting out your current work-around: G_dlgTools->Close(true, HideReasonCode::MdlUnload, true)), then yes please zip and attach the most simplified and portable test case. This ensures we have the highest chance of reproducing your exact code in the least amount of time and can address a/any remaining defects.
Thank you,Bob
Hello Robert,
here's a simple example.a 'ma' with the resources for a toolbox, and a dll with a mdlMain which opens this toolbox.
if I don't destroy the toolbox when Microstation Connect U14 is closed, my program is automatically reloaded when the plan reopens. (same workspace,workset).
Goubier SébastienTestMaDll.zip
The test case you provided in current form does not compile in a modern MicroStation CONNECT Edition (MSCE) Developer Shell. Can you a.) provide exact instructions to compile under the MSCE Developer shell or, b.) update the make files so your code compiles cleanly in a "pure" MSCE Developer Shell environment?
Hi,
ah yes, try with the new files attached (replace Compil.bat and TestMaDll.mki)
Compil.bat : edit line : SET MS=C:\progra~1\Bentley\MicroStationCONNECTSDK\
with your SDK Path (no space)
Then launch Compil.bat
Goubier Sebastien
MAJ.zip