RJ Graffix
My feedback
10 results found
-
6 votesRJ Graffix
shared this idea
·
-
2 votesRJ Graffix
shared this idea
·
-
6 votes
An error occurred while saving the comment An error occurred while saving the comment RJ Graffix
commented
Well, that's a surprise! I've been using Nudge for dash offset since the mid 1990s, and can swear AI used to save the dash offset property. I can confirm that since at least CC 2019 it does NOT save it, or does not read it when re-drawing the stroke.
I agree, even if Adobe doesn't provide a UI for users to access dash offset without a plugin or script, AI needs to save it, read it, and expand it properly.
RJ Graffix
supported this idea
·
-
6 votesRJ Graffix
shared this idea
·
-
3 votesRJ Graffix
shared this idea
·
-
12 votes
An error occurred while saving the comment RJ Graffix
commented
It would be even better if the Tint and Shade functions were available to plugins in the SDK as well.
RJ Graffix
supported this idea
·
-
2 votesRJ Graffix
shared this idea
·
-
4 votesRJ Graffix
shared this idea
·
-
14 votes
An error occurred while saving the comment RJ Graffix
commented
Thanks for the sample file, Egor. That helps a lot. Using AI 27.4.1, the Free Transform tool and Bounding Box widgets both have some issues. The BBAccumRotation tags (and matching dictionary entries) must all be the same in order for it to recognize the rotation. If the compound and its children have no tags at all, they can be created at the same time when rotating them using these tools, and then it works. When objects are rotated, the rotation settings are adjusted individually with each one's compound rotation, which means that if they start with different rotations they'll continue to have different rotations. If you rotate any of the paths before combining them into a compound, you'll probably have this problem.
An error occurred while saving the comment RJ Graffix
commented
Adobe Illustrator has had some weird behavior regarding rotations long before AI 2023, which may compound what's happening here. As objects are rotated, metadata is stored in the objects' dictionaries that track their accumulated rotation. This metadata can be read with Adobe's developer SDK. In a compound path, for example, these dictionaries exist for each of the paths as well as for the compound object that contains them. The same is true for groups, effects, etc.
When you rotate a group or compound path using the Rotate too, that rotation metadata does not get applied to a parent container object, only to the art objects they contain.
When you rotate a *compound path* with the bounding box, it does add the metadata to the parent container. That is not true for groups, however.
Only Adobe's engineers know for sure, but it appears that the Bounding Box does not honor the accumulated rotation info it added to a compound container object. Instead, for groups and compounds it seems to parse each selected object within the group and honors a common rotation that all of them share, or else reverts to no rotation if rotations are mixed.
Reset Bounding Box often doesn't seem to work for me, or gets applied only after changing the selection. It's crazy even without new bugs.
RJ Graffix
supported this idea
·
-
4 votesRJ Graffix
shared this idea
·
I've fixed my Nudge plugin so that it gets around the problem by converting all negative offsets to a positive offset that gives the same result. I'm sure scripts can use the same workaround.