Bug when Setting Artboard Ruler Origins
Ai v 22.0.0
macOS 10.12.6
After updating from CC 2017 to CC 2018, I can now no longer assign individual Artboard Ruler Origins to each Artboard in a document
I use several nested Artboards to control different areas of the same artwork and assign the Ruler Origin of each to the same object. After the update, I can now only assign the ruler origin of one of the nested Artboards to the selected object; the Origin does not change on the others.
I have tried deleting all existing Artboards and then creating them and setting the Ruler Origin one at a time, but once I get more than one in the same area I am no longer able to change the origins.
Mark Morehouse
shared this idea
AdminNitish Agarwal (Illustrator on Web/iPad Team)
(Lead Software Engineer, Adobe Illustrator)
responded
Internal bug tracking ID : AI-4209945
-
Viet Long Dang commented
Thank you, Egor. indeed it works
-
@Viet, 'Change to Artboard Rulers' option is always disabled when you use the Artboard tool, because artboards have to be placed with global rulers. If you pick any other tool, this option works.
Does it work for you then? -
It seems like the bug is still there, I can't turn on the artboard ruler, it is greyed out
-
Merlin
commented
Seemed to have found a fix. Before you can switch to "Change to Artboard Rulers" you have to to show the rulers (View > Rulers > Show Rulers), then double click on the upper left corner of the ruler. If you switch artboards you can do it again to zero to that artboard. At that time you can also "Change to Artboard Rulers".
-
Anonymous
commented
The ruler origin on artboard 2 keeps resetting itself after I've dragged--from the ruler origin crosshairs at the top left corner--the"0" horizontal and vertical points to where I actually want them to be. From this thread, it seems a document can only handle one "0" location (origin) location, and it's on page 1 and that's that. This is ridiculous. If there is a trick to getting the origin point to "stick", it hasn't been revealed here. I don't recall this being a problem in the past.
-
Mark Morehouse
commented
This bug is still alive and well in the latest builds, and will force our studio to keep using CC 2017 until it's fixed. 2 years seems long enough to take care of this, no?
