[CONNECT VBA] Sendkeyin

RE: [CONNECT VBA] Sendkeyin

Oto — Thu, 10 Nov 2016 09:16:19 GMT

for us the shift is 1000 meters

RE: [CONNECT VBA] Sendkeyin

Artur Goldsweer — Thu, 10 Nov 2016 09:00:45 GMT

This could be caused by the selected setting for text justification. From previous tests justification "Top Left" gave correct results with using UOR, all other settings caused a shift.

RE: [CONNECT VBA] Sendkeyin

Oto — Thu, 10 Nov 2016 08:04:26 GMT

This approach also almost work, X coordinate is correct but for some reason Text is shifted by Y coordinate.

pt.x = p.x * UORs
pt.y = p.y * UORs
 

Set oText = CreateTextElement1(Nothing, " Text", pt, Matrix3dIdentity)      
 
ActiveModelReference.AddElement oText

RE: [CONNECT VBA] Sendkeyin

Artur Goldsweer — Thu, 10 Nov 2016 07:47:38 GMT

I can confirm this issue with text origin - Defect 278262 is filed to address this issue and the plan is to have this fixed with Update 4.

RE: [CONNECT VBA] Sendkeyin

Oto — Thu, 10 Nov 2016 07:06:03 GMT

Another issue with CreateTextElement1 that I need to multiply origin with units resolution otherwise it is not correct. But same origin works for cell elements without issue. Is it by design?

Set oText = CreateTextElement1(Nothing, " Text", Point3dZero, Matrix3dIdentity)

pt.x = p.x * UORs
pt.y = p.y * UORs

         oText.Origin = pt
        

ActiveModelReference.AddElement oText

RE: [CONNECT VBA] Sendkeyin

Sumit Deshpande — Thu, 10 Nov 2016 06:30:08 GMT

It is an issue regressed in U2 and is in U3. We had found it earlier but fix failed to make it in U3 for valid reasons. As I mentioned above, this has been fixed in WIP builds of U4.

As a work around for now, you can use text editor or can record text placement script using text editor.

CadInputQueue.SendKeyin "TEXTEDITOR PLACE"
CadInputQueue.SendKeyin "TEXTEDITOR PLAYCOMMAND INSERT_TEXT ""something"""

Or you can use VBA object model as RoadWing and Robert mentioned.

In our reply, we haven't mentioned anything on removal / replacement. Please take a note on this.

RE: [CONNECT VBA] Sendkeyin

Oto — Thu, 10 Nov 2016 05:26:19 GMT

Strange that key-in: "place text;sometext" crashed also but after I placed text with normal dialog it worked afterwards. We have textstyles that are attached from dgnlib so it may be related to fact that no textstyle was active.

I hope place text key-in will not removed as this is useful for placing automatic texts from simple interface tools.

RE: [CONNECT VBA] Sendkeyin

Sumit Deshpande — Thu, 10 Nov 2016 03:16:34 GMT

This issue has been fixed in current WIP builds for update 4.

RE: [CONNECT VBA] Sendkeyin

Robert Hook — Wed, 09 Nov 2016 18:21:46 GMT

Thank you for reporting this issue. I have filed Defect 620571 to be considered for inclusion into a future version release. To work-around this behavior as RodWing suggested, please consider using the MicroStation VBA object model functionality related to creating text.

RE: [CONNECT VBA] Sendkeyin

Rod Wing — Wed, 09 Nov 2016 13:19:59 GMT

It's not just your macro. The same thing happens when you enter those key-ins into the Key-In Browser. I'm actually surprised the Place Text key-in is still available. According to the documentation all of the older text editor interfaces are no longer supported in CONNECT, only the word processor dialog interface is supported for text element creation.

I would suggest you take a look at the CreateTextElement1 function in the VBA Help and use that.