I want use DgnElementECInstance's following API which gives me user friendly property value,
spElementECInstance->GetValueAsString(value, index, false, 0);
however when the ECValue is struct type, I can only get the IECInstancePtr type which don't have GetValueAsString, any suggestions how to get user friendly property value for a IECInstancePtr?
Thanks
Danny
I am trying to create a Macro that I can run in the batch processor to move the bottom left corner of my drawings to the point 0,0. The problem is that these drawings are all located at different locations in model space. I tried just a simple CHOOSE ALL, MOVE, KEY-IN XY=0,0 macro, but because the drawings are all scattered around, it doesn't work correctly. Does anyone have a solution to this problem?
I am trying to create a Macro that I can run in the batch processor to move the bottom left corner of my drawings to the point 0,0. The problem is that these drawings are all located at different locations in model space. I tried just a simple CHOOSE ALL, MOVE, KEY-IN XY=0,0 macro, but because the drawings are all scattered around, it doesn't work correctly. Does anyone have a solution to this problem?
Hello All,
How does one set the text for the headings in a multi column listbox? I do use .AddItem to place things in the listbox if that makes a difference.
Thanks,
Minion
I want to know how to link a DDD cell to a VBA so the user can use the VBA form to populate the DDD?
Ian
Hi Experts,
I have a model and one of the element contains 14 linkages and 1 xAttributes but don't know how to read them all out.
I read out all engineer content associated with this element, and also use following codes to read all xmlFragment properties, seems there still missing some property.
XmlFragmentListPtr linkageFragments = XmlFragmentList::ExtractFromElement(eh);
if (linkageFragments.IsValid())
{
for each (XmlFragmentPtr fragment in (*linkageFragments))
{
if (fragment.IsValid())
...
}
}
When opening this model in the AECOsim Building Designer I saw some properties were not be read out, but I don't know if they are the 14 linkages and also don't know how can I read them out with API.
Hi experts,
I am using DGNPlatform Native C++ version(v5.3.2.56) toolkit independent of MicroStation.
For the extended element type 106, I want to know how get the geometry data for the extended element from the toolkit. Currently, I use the following API to drop the extended element to get the geometry data. Do you think that it makes sense?
DisplayHandler::Drop(ElementHandleCR eh, ElementAgendaR dropGeom, DropGeometryCR geometry)
Justin
Hi experts,
I am using DGNPlatform Native C++ version(v5.3.2.56) toolkit independent of MicroStation.
The following API can get valid IBRepQuery for the smart solid. But it failed for the feature solid. For the feature solid, should I use which API to query the geometry data?
IBRepQuery* pBrep = dynamic_cast<IBRepQuery*>(&elmHandler)
Justin
Hi folks,
I'm trying to use the new ribbon interface to replace my old V8i toolbox in my app. Under V8i I would disable or enable individual icons in the toolbox via calls to mdlDialog_item*() functions. Since I can't control what gets displayed/disabled in the ribbon via direct calls to the SDK, I've been trying to use named expressions hooked into the dialog access strings published as CExpressions, which are then delivered in a DGNLIB file.
For example, if my app is called "MyAppName" and it has a global variable published with the name "MyBooleanVariable", then I can add a named expression "MyNamedExpression" with the expression set to: "Session.EvalCExprAsBool("MyBooleanVariable","MyAppName")", and this seems to work correctly if MyAppName.MA is loaded and the boolean variable "MyBooleanVariable" is published via a call to mdlDialog_publishBasicVariable().
This has caused me to ponder the following questions:
A working example of a custom ribbon would have been really useful in the Connect SDK, but if anyone known any answers here it would also be very helpful.
Dear experts,
The mesh point index from the toolkit API is the negative number. As a workaround, I use its corresponding positive number. Especially, after calling PolyfaceHeader::Triangulate(), the negative number of the mesh point index always appears as follows.
My qusetion: what does the negative point index of the mesh mean?
Dear experts,
I am using 10.00.00.28 MicroStation release. I found that the following API is removed in the toolkit API corresponding to 10.00.00.28 MicroStation release. This API is ever used to get the smart solid body data in the previous toolkit. So, what is the new API to get the smart solid in the toolkit API corresponding to 10.00.00.28 MicroStation release?
SolidsKernelAdmin::_RestoreEntityFromMemory (ISolidKernelEntityPtr& out, void const* pBuffer, UInt32 bufferSize, ISolidKernelEntity::SolidKernelType kernelType, TransformCR transform)
Is there any way to change the font of a run in a TextBlock? The only way I can see is to "Remove()" the Run's text, and "Insert()" it back after setting a new RunProperties (TextBlock::SetRunPropertiesFroAdd() ). I can get a "const" pointer/reference to the current TextBlock's "Run" , so I can't see a way to just assign a new font DgnFont...
I should clarify that I have a "mixed" font TextBlock, and I only want to change certain "Runs" to a different font. I think using ElementPropertiesSetter changes the entire TextBlock, and that is not what I wish to do....
Bruce
The IEEE published its annual appraisal of programming language popularity. Python jumps to No. 1, and Swift enters the Top Ten. R is pretty high on the list.
Hi
If I create a closed curve in Mirostation V8i, and see it in "Smooth" display, the area of the curve will be filled. The picture below shows the closed curve in the display style of "Wireframe" and "Smooth".
In the code, the element is recognized as curve, and will do not go to the code of handling surface.
CurveVectorPtr pathCurve = ICurvePathQuery::ElementToCurveVector (eh);
if (pathCurve.IsValid ())
So my question is that why the closed curve will be filled? For the closed curve, shall I considered it as a curve or a surface? If it is surface, how to get it from toolkit?
Is there any documentation on the absolute basic essentials to implement when porting from V8i mdl's to Connect?. I have written a few mdls in the past and want to now re-compile them for Connect. I have no idea where to start, and am not familiar with Windows programming. I previously made use of Select Series III SDK - I am lost in unfamiliar territory. I am hoping there is a fairly easy way out!
The SDK example ReportsExample shows us how to specify Item Types to be used in a report.
How do we add element properties to a report definition? For example, if my schema should be attached only to closed planar elements, how do I add element metrics such as area and perimeter to my report definition?
It looks like I should call ColumnDefinitionNode::SetAccessors, but ReportColumnAccessor seems to apply only to ECProperties and not element properties.
I create a simple cube mesh in the MicroStation. By the toolkit API, I found that the face normal is outwards(right-handed). The mesh face loop orientation is counterclockwise. Is that always true for all dgn mesh models?
Dear experts,
I create a DGN mesh model. However, I can't get the mesh vertex normal by API PolyfaceHeader::Normal(). In result, the converted mesh looks not smooth. My question: Should all mesh data in the MicroStation carry the vertex normal data? Is there any API to generate the vertex normal for the mesh body?
In MicroStation,
My result(not smooth),
Is the ElementEnumerator object type no longer available while programming a macro? I am trying to edit all the tags in a file at once and want to parse through each tag indivdually; in the past I used an ElementEnumerator but now I am receiving an error that says "Compilation failed at line 6. (the line I defined the ElementEnumerator) Unknown type." Is there a different way of accessing each tag individually?
Hi,
I'm trying to manually convert an add-in that worked in MicroStation v8i so that it works in MicroStation CONNECT Edition. So far I managed to do a couple things that work and I fixed a few errors too. However, I can't figure out why when I include MicroStation.r.h all of a sudden I get tons of errors from that file. I use Bmake to compile outside of visual studio. Here's some of the errors:
C:\Program Files\Bentley\MicroStationCONNECTSDK\include\Mstn\MicroStation.r.h(11) : error: can't open #include file DgnPlatform\DgnPlatform.r.h
C:\Program Files\Bentley\MicroStationCONNECTSDK\include\Mstn\MicroStation.r.h(11) : error: No such file or directory
C:\Program Files\Bentley\MicroStationCONNECTSDK\include\Mstn\MicroStation.r.h(12) : error: can't open #include file DgnView\DgnViewSettings.r.h
C:\Program Files\Bentley\MicroStationCONNECTSDK\include\Mstn\MicroStation.r.h(12) : error: No such file or directory
(etc, same errors for DgnPlatform\Image.h and Mstn\MdlApri\rtypes.r.h)
C:\Program Files\Bentley\MicroStationCONNECTSDK\include\Mstn\MicroStation.r.h(43) : error: 'typedef' : syntax not recognized
I use the MicroStation CONNECT Developer Shell and the environment variables seem to be instantiated correctly.