Place Text through VBA

Unknown said:

CadInputQueue.SendKeyin "place text"
CadInputQueue.SendKeyin sText

In general, if you queue a user key-in using VBA then the result is the same as if you performed that task manually.  In other words, MicroStation can't distinguish between you typing place dialogtext icon and VBA queueing place dialogtext icon.

If a key-in causes MicroStation to pop a dialog, then it will pop that dialog.

If you want to avoid the consequents of a user key-in, then use VBA to create objects directly, in the way that others have suggested.  Search VBA help for examples.  Searching for CreateTextElement1 reveals an example under topic Elements and Levels.

Thanks for the replies. Has basically got what i wanted.

The only thing is that i would like the user to place the text where they would like, is there a way i can put the new text element to the cursor and have the user select the point? rather than define the point?

Unknown said:

The only thing is that i would like the user to place the text where they would like, is there a way Ii can put the new text element to the cursor and have the user select the point?

Write a class that Implements IPrimitiveCommandEvents.  Read about Interface Oriented Programming in VBA help.  Start that class from your form and pass it the string to be created.

Sub PlaceTextInteractive (s As String)
  Dim oTextPlacer As New clsGolding
  oTextPlacer.Text = s
  CommandState.StartPrimitive oTextPlacer
End Sub

Create a class module named clsGolding.  Put the following in that class...

Implements IPrimitiveCommandEvents

Private m_strText As String

[Edit] ' wrong: Public Property Set Text (s As String)
Public Property Let Text (s As String)

  m_strText = s
End Property

'  Add all the subroutines required by IPrimitiveCommandEvents

Sub IPrimitiveCommandEvents_Datapoint (point As Point3d, oView As View)
  Dim oText As TextElement
  Set oText = CreateTextElement1 (Nothing, m_strText, point, Matrix3dIdentity)
  ActiveModelReference.AddElement oText
End Sub

Unknown said:

The only thing is that i would like the user to place the text where they would like, is there a way Ii can put the new text element to the cursor and have the user select the point?

Write a class that Implements IPrimitiveCommandEvents.  Read about Interface Oriented Programming in VBA help.  Start that class from your form and pass it the string to be created.

Sub PlaceTextInteractive (s As String)
  Dim oTextPlacer As New clsGolding
  oTextPlacer.Text = s
  CommandState.StartPrimitive oTextPlacer
End Sub

Create a class module named clsGolding.  Put the following in that class...

Implements IPrimitiveCommandEvents

Private m_strText As String

[Edit] ' wrong: Public Property Set Text (s As String)
Public Property Let Text (s As String)

  m_strText = s
End Property

'  Add all the subroutines required by IPrimitiveCommandEvents

Sub IPrimitiveCommandEvents_Datapoint (point As Point3d, oView As View)
  Dim oText As TextElement
  Set oText = CreateTextElement1 (Nothing, m_strText, point, Matrix3dIdentity)
  ActiveModelReference.AddElement oText
End Sub

Thanks Jon,

I haven't been able to get that to work unfortunatley.

I have done as above...

-Created a Class Module called "clsGolding" which has the following in it... But when run the below error appears.

My form has a button that simply is this

 PlaceTextInteractive ("testing")

Which controls this

Sub PlaceTextInteractive(s As String)
  Dim oTextPlacer As New clsGolding
  oTextPlacer.Text = s
  CommandState.StartPrimitive oTextPlacer
End Sub

What have I done wrong?

See the highlighted portion of your code? Thats the error. Unfortunately the Screenshot is too small, could not read it.

But I can see it is not the part you copied into your mail.

I understand the highlighted part is the error but not too sure why its appearing.

I have attached the picture rather than embed it.

Thanks for the replies guys.

Your Property needs a Getter! Google your error text, you will find an answer.

Syntax of Class Properties

When you write a class property with VB/VBA...

• use the Set keyword when assigning an object
• use the Let keyword when assigning plain old data (POD), such as a number or string
• use the Get keyword to extract data from the class

In your screenshot, the incomprehensible error message is trying to tell you to use Let rather tha Set in your Text property.  Try this instead:

Public Property Let Text (s As String)
  m_strText = s
End Property

Apologies

Unknown said:

What have I done wrong?

Nothing! That was my fault for writing the wrong keyword in my example below.  I'm always forgetting to use Let for PODs.

Unknown said:

Your Property needs a Getter!

A VB/VBA class property lets you assign data to an object or get data from an object.  You can write either or both properties, although it's usual to write both.

• A class having only a Set or Let property is write-only
• A class having only a Get property is read-only
• A class having both Get and Set or Let properties is read-write

Thanks Jon, much appreciated. I'm still a relative newbie to all this. Its a hell of a learning curve!

Its skipped over that part but now it comes up with another message.

Compile error:

Procedure declaration does not match description of event or procedure having the same name

Its highlighted the ...

Sub IPrimitiveCommandEvents_Datapoint(point As Point3d, oView As View)

Unknown said:

Sub IPrimitiveCommandEvents_Datapoint(point As Point3d, oView As View)

The exact signature is

Sub IPrimitiveCommandEvents_Datapoint(point As Point3d, ByVal oView As View)

Is the compiler happier with that?

Happier :)

---------------------------

Microsoft Visual Basic

---------------------------

Compile error:

Object module needs to implement 'Keyin' for interface 'IPrimitiveCommandEvents'

has highlighted

Implements IPrimitiveCommandEvents

Unknown said:

Object module needs to implement 'Keyin' for interface 'IPrimitiveCommandEvents'

In VB/VBA, a class that Implements an Interface must have all the subroutines of that Interface, even when they do nothing.  In other words, you must write all the subroutines required by IPrimitiveCommandEvents.  Fortunately, the IDE provides some assistance:

1. Top-left is a combobox having a list of classes and interfaces in your current project
   1. Choose IPrimitiveCommandEvents
2. Top-right is a list of procedures for the current class or interface
   1. As you select each procedure, VBA writes a skeleton for that procedure
   2. Repeat and rinse for each procedure