![]() To pick up on Stefan's reply below, for me, as a developer creating solutions that integrate with MS Word, there is no "hard to tell" about this - not having fully capable macro recording is a bug. Your workaround works in Word 2013 - I thank you, and I think it should be an answer to this thread until Microsoft fixes macro recording. DOCX file.Įxcellent work XianZomby - I use macro recording to help me explore the Word API when developing add-ins - and had I not read your reply, I would have given up on this method in Word 2013. The same does not hold true if I am editing a. DOC file, there's a number of mouse-related commands I'm able to record with the macro recorder. There, it seems, it considers those two sets of absolute coordinates, not a set of coordinates and then an offset.īut back to macros: when using Word 2010 to edit a. That same subroutine produces a mess inside a DOCX file. Here, it seems, the second set of coordinates in each instruction is a delta for how much either the X or Y should change. DOC file, in Word 2010, this macro produces an isosceles triangle:Ī(msoConnectorStraight, 200, 100, 20, 30).SelectĪ(msoConnectorStraight, 220, 130, -40, 0).SelectĪ(msoConnectorStraight, 180, 130, 20, -30).Select ![]() DOC will not always work correctly - in particular, "line" does not faithfully reproduce, though it seems "curve," "freeform," and "scribble" do. DOCX file, the drawing macro I created while editing as a. DOCX file, the macro recorder will not record my drawing efforts, and instead produces an empty subroutine.Īdditionally, while in the. However, if I am editing a newly created. Then the macro will faithfully recreate those steps and draw the same picture. DOCX), the macro recorder will record the commands I issue with the mouse to draw a picture. In Word 2010, if I am working with a newly created and already saved.
0 Comments
Leave a Reply. |