[vba-v8iss3-v8 2004] v8i longer than v8

Hi Laurent,

what does it mean "so longer"? Is it ten times longer or even a hundred times? There is no guarantee API has the same speed in different versions. Many things has changed from V8 2004 Edition inside MicroStation, which is probably the reson of the different speed.

Because there is no profiler available in MicroStation VBA, you should add a time counter to your code to check what step takes the most of the time.

In my opinion your code is not very realistic, to use SendCommand, which simulates a user interaction, in a loop is nothing than should be found in well written code.

So I think the target is not to discuss why one version is different to another (well, if it's hundreds time slower, of course report is as a bug), but if you will be able to identify what line is slower, to find a way how to optimize the code or to do the same thing in a different faster way.

With regards,

 Jan

Hi Laurent,

what does it mean "so longer"? Is it ten times longer or even a hundred times? There is no guarantee API has the same speed in different versions. Many things has changed from V8 2004 Edition inside MicroStation, which is probably the reson of the different speed.

Because there is no profiler available in MicroStation VBA, you should add a time counter to your code to check what step takes the most of the time.

In my opinion your code is not very realistic, to use SendCommand, which simulates a user interaction, in a loop is nothing than should be found in well written code.

So I think the target is not to discuss why one version is different to another (well, if it's hundreds time slower, of course report is as a bug), but if you will be able to identify what line is slower, to find a way how to optimize the code or to do the same thing in a different faster way.

With regards,

 Jan

in  Microstation -VBA manner I would

replace the scaling "CadInputQueue.SendCommand" with the MVBA equivalent tool set. Ther are plenty of examples in the help-file and indeed in the forum.

Ok Jan and Frank,

I undestand...

In my real vba, i use the command "construct line minimum" between two elements: a point (lineelement in fact) and a ComplexStringElement ( Which I get subelements )

So I Apply this command (construct line element) to each subelement 

getLastValidGraphicalElement and compare the lenght of each lines ( keep the minimum length  and the endpoint of the line)

So I don't find the good way in vba to  place a minimum line between a point and a element

Sorry for my poor English, Merci

Laurent

Hi Laurent,

Unknown said:

In my real vba, i use the command "construct line minimum" between two elements: a point (lineelement in fact) and a ComplexStringElement ( Which I get subelements )

I think (but have not tried it) you can use mdlMinDist_betweenElms VBA wrapper.

Unknown said:

So I don't find the good way in vba to  place a minimum line between a point and a element

Function mdlMeasure_closestPointOnElement can be the solution.

Unknown said:

Sorry for my poor English, Merci

Don't worry about English, there is no English native speaker in this discussion involved so far :-)

Regards,

  Jan

Thanks Jan

I 'll try

May be ProjectPointOnPerpendicular2 can help too

Laurent

Unknown said:

Don't worry about English, there is no English native speaker in this discussion

Pwah!  Mais je suis un observer, qui speaks bien le franglais.  Mon biggest problème est ce que le technical vocabulary is too petit, et le VBA Help n'a pas any translations français.  Bien sur, Let's Parler Franglais!

Merci de cette pointe d'humour Jon ,

C'est exactement ça !

Cordialement

Laurent