Browse By Tags

Greetings Turkay, This type of data manipulation is best done programmatically. If you could provide a sample design file and details on what elevations should be moved to which levels, I would gladly craft a sample VBA application which could be used…

Robert, Your VBA program is sending GDI keyins which unfortunately do not provide the ability to specify the WHERE clause. There are however ways to use the GeoDataInterchange .NET API wrapped up as a COM server, exposing to VBA ways to specify WHERE…

I reviewed the provided text2xfm v1.5 application and it appears the ability to process multiple text elements still exists. If a " Fence " is active when the " Process " button is pressed then all of the text or text node elements in the fence contents…

Robert, Use of collections in sub-features is not currently supported.

Bjorn, Yes, features can be renamed programmatically using code that updates the .name and .alias properties on the feature instance then calls the .write method. Attached is a VBA example which illustrates one way in which this can be done. rename_features1…

Bruce, I appreciate the additional sample data. I've been out of the office for the past few days travelling on business but earlier today using the new data I ran the attached promote2.mvba process which created 4 new polygon collection feature instances…

Bruce, After a quick review, I believe your use of the DFS rules file is causing the observed difference when running the promote1.mvba process. I will perform some additional verification testing and update you with my findings. Question, I noticed…

Bruce, Please zip up and send me via private message... Your modified MVBA file. A sample design file containing the original MicroStation shape elements. A current copy of your Bentley Geospatial Administrator schema file. ...and I will…

Martin, Is the printing app to which you refer unable to process the XFM V1 08.11.07.xx formatted file? I suggested that to potentially eliminate the need to process the XFM V2 08.11.09.xx formatted file. Attempting to read the fill and pattern information…

Martin, Using your data and code have been able to replicate what you are reporting. I'm working now to determine if this is a previously unreported defect. I will update you my findings once complete. I would be interested to know more about what…

Martin, The shape elements are stored as sub-features in the XFM type 106 polygon collection. The following bold Bentley Map VBA code should give you an idea of how you can traverse the polygon collection and obtain information from each sub-feature…

Jan is correct. No VBA wrappers are provided for the Bentley Map C API functions. The most commonly used Bentley Map functionality, including the XFM data modeling engine is provided in the XFT (XFM Feature Toolkit) COM object. Use of other Bentley Map…

Erik, You sample code works fine after adjusting the ZoomFactor argument such as follows: oFeature.ZoomInView CommandState.LastView, 1#, 50#, True I would also recommend setting the last argument to True to handle those features which may have…

Greetings Erik, Using XFT the following approach should work. Dim plotscaleTypeString Dim plotscaleTypeValue As New xft.InputValue plotscaleTypeValue.SetTypeAndValue ValueType_DWGSCALENAME, "" plotscaleTypeString = plotscaleTypeValue.EvaluateAsString…

Erik, I've tested using .91 and .95 builds with both performing the ZoomInView method as expected. I will have some of my other colleagues perform independent tests after which I will contact you with results.

Erik, As suspected it appears the proper transform is not being applied when the VBA code is started directly from the "Project Manager" so I've filed an issue to have the matter resolved in the upcoming Bentley Map V8i (SELECTseries 3) 08.11.09 maintenance…

Ruben, I'm not aware of any specific VBA that converts XFM business properties to equivalent MicroStation tags. However using the "XFM Feature Toolkit" (XFT) one can read the business properties of an XFM feature instance with the following: …