[C++ Connect] Exception when using mdlSystem_enterGraphicsExtended(0)

Hello Hervé,

we used this in early V8 day, too. But we found most of our topics could be solved without having the user-interface waiting for us. So we uses only MS_DGNAPPS today.

I guess, only if you want to manipulate a DGN without any user interaction it is - in my opinion -  a opportunity to use MS_INITAPPS , but to close MicroStation directly afterwards.

And another problem. If you start a MicroStation without user interface, you could produce "license overusage", because the user is not aware, that a MicroStation is still running.

Just some thoughs :-) 

Hello Volker,

The goal of this is to launch Microstation with our own interface : we have redevopp the file manager. So the graphic session is opened but before having the classical interface of Microstation, the user has to chose his file with our own file manager.

In fact, this problem happend since the Connect Editon Update 13, it was working well before...

Thanks for your help,

Hervé

Herve Cuzon said:

this problem happend since the Connect Editon Update 13, it was working well before...

I think you have found a bug with mdlSystem_enterGraphicsExtended!  You have already provided an example project.  I suggest that you post a Service Request (SR).

Herve Cuzon said:

I've already shown this problem to a Bentley developer during the BDN Conference in London last September

That would have been Paul Chater or Robert Hook?  Unfortunately that informal approach does not guarantee that he logged a defect!

Hi Hervé,

Just an idea for a workaround: Open MicroStation with an empty DGN (like PowerDraft offers) and open at first your own dialog. Maybe not the best workflow, but it may help, till someone from Bentley give you some hints how to work with mdlSystem_enterGraphicsExtended .

I've already shown this problem to Bentley developper during the BDN Conference in London last September...

Herve Cuzon said:

I've already shown this problem to Bentley developper during the BDN Conference in London last September...

I agree with Jon: Despite of people like Bob help a lot, when bug is discovered, it's not enough. Defect number has to be assigned and (optionally, but recommended) linked with Service Ticket which represent a link between the bug and the user/customer/developer interested in a fix.

Without knowing Defect number, the bug does not exist from developers' perspective.

Regards,

  Jan

Hi Herve Cuzon,

Please Note. There are times where it may be best to provide/post a simplified TestCase to ensure the highest possibility of others being able to see and reproduce your (exact) issue and conditions, and provide quicker review and response times.

Since the issue you describe is a quick and easy item to wrap up and test internally, I will create the simplified test case to see if I can reproduce the very simple condition and result you are mentioning.  I hope to provide a review of this today and update this thread as long as time and priorities permit me to do so (promptly).  I will update with a reply of my results.

Thank you and HTH,
Bob

Hi Bob,

I post a complete sln in my first post.

Did you find it and try to compile it?

Regards,

Hervé

Hi Herve,

No I did not see that I yes, I will review that (soon).

Thank you,
Bob

Hi Hervé

Can you give some more information on the exception you are finding ?  Is the exception getting out of your call to mdlSystem_enterGraphicsExtended into your code ? 

I could not reproduce an exception being thrown in Microstation in U13 or U14. What exceptions are you setting your debugger to catch ? Is this exception causing a specific problem for your code ?

Regards

Paul

Hi Herve Cuzon,

Sorry for the delayed reply. I downloaded and attempted to compile your project unsuccessfully since it was not in the form of a test case.  I will try to make some time to create a test case example that will likely work fine (as Paul commented works), although maybe as you add your code to the example you can find out specifically what changes may cause a portable and reproducible break that we can examine.  I will update this thread with the test case example as soon as I can create it.

Thank you,
Bob

Hi Herve Cuzon,

Sorry for the delayed reply. I downloaded and attempted to compile your project unsuccessfully since it was not in the form of a test case.  I will try to make some time to create a test case example that will likely work fine (as Paul commented works), although maybe as you add your code to the example you can find out specifically what changes may cause a portable and reproducible break that we can examine.  I will update this thread with the test case example as soon as I can create it.

Thank you,
Bob