Hi,
thanks a lot for your answers. I'm suspecting MicroStation instantiates the VBA/MDL-setup in different ways.
- Starting the macro using the key-in or starting it directly from the VBA-editor in the following way "Selecting the modul in the project explorer->Hit F5-> Dialog "macros" select the correct macro and start it" leads to the correct behaviour.
- Starting the macro using the button in the user form (as mentioned already) or placing the cursor in the source code (VBA editor) of the macro and hitting F5 leads to the wrong behaviour.
In my opinion there have to be differences.
Jon Summers:
.... For MDL, there are substantial differences between MicroStation V8.5 and later versions. Not least are invisible differences in the user interface.
Is there a version of the 3rd-party MDL app. built for MicroStation V8.5?
Jon Summers:We are in close contact with the 3rd party developpers and did a lot of tests before. The 3rd party is very conversant with developping apps for MicroStation. They've started in the 1990's with MicroStation.
They're delivering builts for v8.5 and v8i s2/s3. As I know loading builts for newer MS Versions in v8.5 isn't possible. v8.5 throws an error message.
We've also noticed that there was an essential change (the data structure identifying the vba event) between the MDL-SDK for s2 and s3 concerning the handling of VBA triggered events.
stefan_bernsdorf:
Ingo,
is there any special reason, to use this 3rd party tool for user interactions?
Yes, we're using a digital photogrammetric system. That means same data point have to be measured in different views.
stefan_bernsdorf:
You can implement mouse event routines in VBA too.
Regards, Stefan.
What do you mean in detail?
Many thanks in advance.
Best regards.
Ingo