why cant i draw a straight line or arrow in word 2013?

Anonymous
2014-01-04T08:05:17+00:00

hi

in word 2013 when I want to draw an arrow or a line it cant be straight in 180 degree in page and it is always a bit curve to up or down for example draw a rectangle and on its border line draw an arrow ( the arrow must be exactly on rectangle border line ) and you will see that the arrow is curve and is not on rectangle border.

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-03-21T15:41:48+00:00

This is easy to recreate, but can be solved by setting the height or width to zero in the ribbon.

Was this answer helpful?

100+ people found this answer helpful.
0 comments

81 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-04-20T09:45:45+00:00

    Still happens with Word 2016.

    Was this answer helpful?

    0 comments
  2. Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
    2017-04-20T12:04:48+00:00

    Lihat jawaban oleh Stefan Blom, tanggal Octobre 27, 2016

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-20T14:45:53+00:00

    Note that the original post in this thread discusses a concrete bug with Line shapes in Word 2013 which probably won't be fixed. On the other hand, there is a simple workaround available.

    You can post feedback on Microsoft Word in the Uservoice forum at http://word.uservoice.com.

    You don't mention what's the "simple workaround". Tony Jollans' answer is an acceptable workaround, if that's what you meant then you should mention it explicitly (and/or quote him).

    However, this also means that the bug isn't fixed in Word 2016, and workaround needs to be used.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-04-20T14:47:07+00:00

    Stefan's answer doesn't mention what's the "simple workaround". Tony Jollans' answer is an acceptable workaround, if that's what he meant then he should mention it explicitly (and/or quote him).

    However, this also means that the bug isn't fixed in Word 2016 (as I said), and workaround needs to be used.

    Was this answer helpful?

    0 comments