How do I disable Connect project chooser dialog when using Multiframe COM automation interface. Multiframe requires user input at this dialog (either cancel or select a project) - takes away from the whole point of using COM interface. For our purposes, the file does not need to be associated with a project.
Any updates to this issue for version 22 of Multiframe which now requires the user to be logged into Connection Client to verify software license. Previous answer worked for older versions using SelectServer, but not with the new SES. Any way to control the Project Chooser window via COM?
Sorry - just reread original question.
SO there is one key to prevent the "Connect fail" message dialog coming up; there is another key to prevent the project chooser coming up
they need to be in the registry area that corresponds to the version you are using - ie 21, or 22 (or 23 which will out soon)
Thank you. I am using version 22, recently upgraded from 21. I had to add the line to the registry and then set to zero and it worked to suppress the Project Chooser dialog window. However, the COM application takes significantly more time to run. When registry setting is set to 1 and I click Cancel on the Project Chooser dialog during the COM application, the application takes 27 seconds to run. When the setting is set to zero (dialog is suppressed), it takes 215 seconds to run. It seems to be checking against the Bentley Cloud Services after every command. Screen clipping of the status bar is below (the green status bar continuously flashes while COM is running). When the registry setting is set to 1, the status bar never displays this message, there is no delay.
As a second test, with Multiframe closed, I set the registry setting to zero, re-started Multiframe and tried drawing members in a new project. There is an obvious delay after every command. With Multiframe still running, I clicked on Bentley Cloud Services, chose Associate Project to prompt the Project Chooser Dialog, then clicked cancel on that dialog. After doing that, there is no longer a delay after every command.
What is causing the delay? I need the COM application to runtime to be closer to 27 seconds with the Project Chooser dialog suppressed.
thanks for the extra detail, are you able to share your VBA? code that accesses Multiframe through COM so that we can attempt to see what might be going on?
James Clarkson Jason Yang
This happens even with the sample automation "GeneratePortal.xls" included with the Multiframe install. Here are links to screen recordings captured while the GeneratePortal is running:
With registry setting set to zero (Project Chooser Dialog suppressed): https://www.screencast.com/t/o1zLTV7JImV Note the status bar continuously displaying "Waiting for Bentley Cloud Services"
With registry setting set to one (clicking cancel on Project Chooser Dialog): https://www.screencast.com/t/9d0CN8hqwc2
I've seen one other user with this happening. Can you please try associating your file with a project. You will need to register a project, you call it anything with any reference number.
We found that by associating it with a project, Multiframe stopped looking for a project and the delays went away.
Can you please let me know if it resolves it for you? We are working on a permanent fix.
I don't want to associate it with a project. I am using COM automation to run an analysis in Multiframe from Excel. I have no need to associate it with a project, it is a one time run only. We use Multiframe as the analysis engine, exporting all the results back to Excel for further manipulation. Having to associate with a project requires the user to manually click on cancel in the Project Chooser dialog (or pick a project) - the automation is stalled until the user responds. That defeats the purpose of running Multiframe via COM. Why can't the project chooser dialog by suppressed and Multiframe not look for a project after every command? Can a line of vba code be created to cause the same effect as the user manually clicking cancel on the Project Chooser dialog?
we have disabled the project chooser entirely for the next version it will only be accessible from the menu. in previous versions 22 and 21 etc. It was a requirement imposed on us by Bentley that the project chooser be displayed as soon as the model was initially created -- its just something we were mandated to implement. It was something we felt didnt necessarily fit in with the majority of Multiframe users' workflow - but we didnt have any choice and were audited on the implementation. However we have decided to make it so that the ProjCh dlg is now only show if the menu item is specifically selected -- this will solve your problems in the next release.
In the meantime, you should be able to set a dummy project via COM and that should prevent the ProjCh dlg from coming up.
Ive tested it on my machine with Multiframe 22.03.00.121
I call the following -- its just a random GUID that I generated and it seems to work as far as I can see.
this is before it starts adding geometry
mfApp.Frame.CONNECT_ProjectGUID = "525351A1-26A2-4912-9500-210F50CE4AA4"
hopefully that should get you working until the new version is available.
Answer Verified By: Trevor Veitch
That worked. Thank you. I appreciate our user feedback & coordination leading to improvements for the future versions of Multiframe.