More work, that is, for whatever guys end up posting the code here. Thirdly, to specifically copy one object to another place, using sendcommand, will actually take MORE work than doing it correctly, using VBA.
You'll run into all sorts of strange bugs that will be near impossible to trace they may appear as different problems on different machines. Secondly, you dont wanna use it in "more complex" cases, because, since your VBA code wont know if a problem occured, or if its done running (and your code immediately jumps to the next command ) Its like running a DOS batch file from VBA - you have no idea if everything went ok, and, if its doing a lot of work, you WONT EVEN HAVE ANY IDEA IF ITS DONE RUNNING YET. Its a kludge, a workaround, and like "Goto", should be avoided at any and all costs. I will really appreciate if you can help me!įirstly, "proper implementation" and "SendCommand" arent normally used in the same sentence. if I have programatically created an object (arc) and I have two points taken from the interaction with the user, how can I copy objArc from Pt1 to Pt2 with SendCommand method! If I can figure out this SendCommand may be useful in more complex cases.
#TXTEXP AUTOCAD MAKES WEIRD LINES HOW TO#
I just need the proper way of implementation of sendCommand, and especially I would like to know how to refer in SendCommand to programatically created objects,Į.g. Actually I don't need the SendCommand method for creating arc, I gave this example just for simplicity.
0 kommentar(er)
