Get UserParameter values for FormattedText in ModelState members.
Hi @AlexTRK. I haven't tried it quite the way you are talking about here, but you could create a String type variable on a previous line of code, and set its value the way you want it, then use that variable instead of the 'FullDocumentName' portion of code you are using in that line of code shown. In that previous line of code, don't use the actual 'FullDocumentName', but instead use 'FullFileName', then add the "<YourModelStateName>" portion to the end of it, to specify the ModelState you want to target, instead of the one that is currently active in 'ThisDoc'. Do you understand what I mean there? When working with a 'model' type document, and ModelStates are involved, the property 'FullDocumentName' is basically just the FullDocumentName, immediately followed by the name of the ModelState that the document is currently under the influence of, and that ModelState name is within "<" & ">" brackets. You could simply create your own String value to use, instead of using the document's 'active' value.
Wesley Crihfield
(Not an Autodesk Employee)
Hi . The best way to learn how to format it, is by reverse engineering & looking at examples. For instance, you can use an 'InputBox' to show yourself the 'selectable' text of the value behind the FullDocumentName of a document, by putting that value in the 'DefaultResponce' portion of that line of code, like the following line of code.
a = InputBox("", "FullDocumentName", ThisDoc.Document.FullDocumentName)Notice there is no space between end of the FullFileName portion, and ModelState name portion.
Now, with that in mind, we can create our own String type variable, and set its value the way we want it to be formatted, which is similar to the FullDocumentName from the above example, but instead of the ModelState name it is showing, we can put a different ModelState name in there, as long as that ModelState exists in the document.
Below is an example of what I was trying to tell you about. Also notice that by default, when you first create a new ModelState using the mouse commands, there is a space between "Model" & "State", but there is no space between "State" & "1", unless you have renamed the ModelState differently than its default. Spelling, capitalization, and spaces are critical. First we create the variable here, and set its value as described.
Dim FDN As String = ThisDoc.Document.FullFileName & "<Model State1>"Now use that 'FDN' variable in the following line, instead of how you were doing it before.
"<Parameter ComponentIdentifier='" & FDN & "' Name='UserParameter' Precision='2' ></Parameter>"Wesley Crihfield
(Not an Autodesk Employee)
Maybe it has something to do with my Inventor installation or how I'm creating the views but this code:
Dim oSheet As Sheet = ThisServer.Documents.Add(DocumentTypeEnum.kDrawingDocumentObject).Sheets.Item(1) Dim oPoint As Point2d = ThisServer.TransientGeometry.CreatePoint2d(10, 10) Dim oView As DrawingView = oSheet.DrawingViews.AddBaseView(ThisDoc.Document, oPoint, 1, ViewOrientationTypeEnum.kRightViewOrientation, DrawingViewStyleEnum.kHiddenLineDrawingViewStyle) Dim oNote As GeneralNote = oSheet.DrawingNotes.GeneralNotes.AddFitted(oPoint, "") Dim FDN As String = ThisDoc.Document.FullFileName & "<Model State1>" 'I've even tried 'ThisDoc.ActiveModelState' here is well. oNote.FormattedText = "<Parameter ComponentIdentifier='" & FDN & "' Name='DParm' Precision='2' ></Parameter>"
With these user parameters:
Creates this drawing:
If we're referencing the document correctly now then it could be an internal bug... very strange.
I think I may see the problem now that I am seeing the entire code. I think it is because you just created a new drawing document, and it has not been saved yet, so it will not have a value for FullFileName yet, and the term ThisDoc.Document' may be pointing to that new drawing document, instead of to the model document. And even if it was pointing to the model document, if that has not been saved yet either, you will have the same problem...no value for FullFileName. I have not messed with FormattedText contents for ModelState specific values much yet, so I'm not 100% sure if everything is stable there when the contents are created entirely by code yet. Plus I'm still using 2022, so there may have been some updates in 2023 that I do not have available for testing.
What you may need to do, in order to get the FormattedText right, is to create it exactly the way you want it manually, using the Format Text dialog, and its nice tools made just for this, then retrieve the results by code, and look at its FormattedText contents. If you use the InputBox trick I showed you above to do this, then you could copy/paste that results text back into your code to set the value properly...if what you are trying to do is possible.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @SašoPrijatelj. I still do not know where that odd String value comes from, but did notice that it did seem to be consistent per ModelState name. I have checked the 'InternalName' of the Document objects associated with each ModelState, but those are formatted differently. I also checked the AttributeSets associated with each ModelState, but there were none. I even guessed at a few possible 'hidden' property names, but none of them worked.
Wesley Crihfield
(Not an Autodesk Employee)
