RE: [V8i C++] Use of std::vector in mdl functions
I would say that reserve is probably not the correct choice here as that is only allocating the memory for the push_back, but it is not setting the count\size of the vector.. I assume that mdlLinear is...
View ArticleRE: [V8i C++] Use of std::vector in mdl functions
[quote user="Bruce Reeves SRNS"]I'm attempting to utilize a std::vector<DPoint3d> as a parameter to mdlLinear_extract()[/quote]Excellent! More info about the Standard Library and MDL.[quote...
View Article[V8i C++] Use of std::vector in mdl functions
I'm attempting to utilize a std::vector<DPoint3d> as a parameter to mdlLinear_extract() without success. Is this even possible? I'd trying to avoid using dlmSystem_mdlMalloc() type functions for...
View ArticleRE: VBA data point is honoring cursor location not memory
Jon, thanks for the helpful reply... I have something that is sort of working... but as I stated I am a novice.I am in v8i 8.11.09.832My 2 remaining problems with the following code... 1) I am trying...
View ArticleRE: VBA data point is honoring cursor location not memory
[quote user="Troy Woodyard"]ph.SetValue "3"[/quote]The underlying data type of Element.Color is Long. You're attempting to set its value as a String. After you modify an element, you must rewrite it...
View ArticleRE: VBA data point is honoring cursor location not memory
(Please visit the site to view this file)unfortunately it still bombs out at the ph.setvalue 3 line
View ArticleVBA data point is honoring cursor location not memory
All,I am new to programming (meaning not good at it.) I am trying to write a simple vba script that calls a microstation utility (text to node). It works fine if I comment out the bolded line of...
View ArticleRE: VBA data point is honoring cursor location not memory
Got it... apparently the "ViewDependent" attribute is boolean not string. Thanks for the help.
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
Hi Bruce,[quote user="Bruce Reeves SRNS"]What ties the display of XAttribute data[/quote]To be precise they are not XAttributes (it's mechanism how the data are stored) but EC data attached to...
View Article[V8i C++] XAttributes and Element Information dialog
What ties the display of XAttribute data to the Element Information dialog? When I select all the elements in my model, I see numerous entries in the Item Browser for a particular XAttribute "class"...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
[quote user="Jan Slegr"]To be precise they are not XAttributes (it's mechanism how the data are stored) but EC data attached to element(s). Element Information dialog is not able to display "any...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
Hi Bruce,[quote user="Bruce Reeves SRNS"]In the image, the 4 elements that are showing up are "simple" elements[/quote]That's correct: If EC data is attached to simple elements (I guess it's true also...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
[quote user="Jan Slegr"]What will happen if you will "location and display" functionality of Item Browser? What element is highlighted if you select a particular Gravel Roads And Areas item in the...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
Is it possible to share the design file? It seems to be the file content specific issue, so general discussion "how it should be" seems to be not efficient. Regards, Jan
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
In paring down the file so there are only two elements (both Lines). I see some unexpected things via the Element Info dialog: 1) On the element that is NOT showing the EC Data, I have two linkages...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
To obtain a complete picture: How EC data were created and attached to elements:By some Bentley applicationManually using ecx addinYour application using C++ codeUsing EC Framework SDK (NET API)The...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
There are 4 possible XAttribute handler IDs associated with ECXAttributes, 1 for each combination of stored vs external schema and hidden vs visible ECInstance. I don't have the exact IDs handy at the...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
To follow up...56ff0001 indicates a visible ECInstance associated with an external schema. Make sure you have registered your schema with ECObjects so that it can be found; if we can't find the schema,...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
[quote user="Paul Connelly"]To follow up...56ff0001 indicates a visible ECInstance associated with an external schema. Make sure you have registered your schema with ECObjects so that it can be found;...
View ArticleRE: [V8i C++] XAttributes and Element Information dialog
"External schema" means the ECSchema is not stored in the .dgn file. Instead it must be located at run-time, e.g. in some directory on the file system. This is what your 56ff0001 handler ID means. You...
View Article