We are are porting a set of MDL applications from MS V8i SS10 to MS CONNECT Update 14.
This includes the set of mdlCntr_xxx MDl functions, which are available in the V8i API, but not in the MS CONNECT MicroStationAPI. At a first glance I couldn't find any adequate set of functions.
So question is: What to use instead ?
As far as i know mdlCntr essentially is a list or a map. Is that the way we have to go ?
Any hints or pointers are appreciated.
Thanks in advance
Martin
Sorry, but why do you not respect the best practices (do not duplicate posts) and not moved this your question? It leads to confusion what discussion is active one and in what to answer.
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Martin Gitschel said:As far as i know mdlCntr essentially is a list or a map
The V8 mdlCntr_xxx family manages containers for raster attachments.
mdlCntr_xxx
Robert Hook developed some migration tools that may help in your case. Look in folder \SDK\MigrationTools.
\SDK\MigrationTools
Regards, Jon Summers LA Solutions
Hi Jan,
Sorry, but I didn't find an entry for the "MicroStation Programming Forum" in the dialog of the More->Move Tool.
Obviously I'm not able to remove the original post from the general Developers and Programming Forum.
Sorry, Martin
Hi Jon,
thanks for your answer ...
But in the remap file (0811to1000Published.remap) there is no entry for "mdlCntr_"
Martin Gitschel said:But in the remap file (0811to1000Published.remap) there is no entry for "mdlCntr_"
Yes, it's correct.
In my opinion the functions have no 1:1 replacement in CE API.
I have not worked too much with rasters yet in CE, but I think may functionality is available using classes like DgnRaster, DgnRasterVector, DgnRasterCollection etc.
Maybe to share more details what functionality is implemented using mdlCntr_functions would help to discuss the best migration strategy.
I assume Robert Hook will be able to share more information ;-)
thanks for answer.
In our case mdlCntr_xxx family is not used in connection with raster files.
It is used as a simple map for mapping of old GG Graphic Group) numbers to new GG numbers when moving MicroStation elements from one DGN file to another DGN file (Just moving of element groups to another file or merging of DGN files).
Martin Gitschel said:It is used as a simple map for mapping of old GG Graphic Group) numbers to new GG numbers
I assume for these types of operations, the current C++ standard offers a lot of generic tools like std::vector, std:map etc.
With regards,
Innovative! Consider using the C++ standard library. The std::map class may do what you need.
std::map
Thanks, Jan
this is exactly what i expected to do when we got confronted with this problem.
I wanted to check if there is some other way available for solving the problem.
Thanks for your answers. Also thanks to Jon.
Best regards, Martin
Martin Gitschel said:I wanted to check if there is some other way available for solving the problem.
When a functionality exists in C++ Standard Library (std::), it's probably always the best solution to use it.
Many pieces of old MDL API was created to standardize often used functionality, because there was nothing like STL, Boost etc. available. Now, when we migrated to C++ and C++ itself is developed actively, there is no reason to prefer proprietary solutions.
Answer Verified By: Martin Gitschel