AdminEgor Chistyakov
(Admin, Adobe Illustrator)
My feedback
6460 results found
-
1 vote
An error occurred while saving the comment -
1 voteCompleted (Comments Open) ·
AdminAvinash Singh Kotwal
(Principal Product Manager, Adobe Illustrator)
responded
This feature has been released in 24.3. Please update to the latest version to use this feature. We would love to hear your feedback.
An error occurred while saving the comment 14 again (about a point at x-hight).
Now it snaps all right! ...except for the 'align 0' liesAn error occurred while saving the comment 28 again. I can’t attach the GIF for it, so there’s a link to the direct link to the image:
https://dl.dropboxusercontent.com/s/5mu0r33l5ot6r3g/snap_priority.gifAn error occurred while saving the comment 30. I was not able to make angular guides work, until I force a single glyph snapping. After it’s released, there are no angular guides again. Another GIF shows me trying to build a specific continuation, bu Ai highlights the center of already created path and won’t draw an intersection I need. So finally I create a next point almost randomly and then move it in place — not great.
An error occurred while saving the comment 29. Ai won’t draw an intersection of angular guide and glyphbound guide :(
An error occurred while saving the comment 28. Well, angular kind of works... But I have a lot of issues with prioritizing. Ai tends to ignore it almost fully, preferring a point that is very far away from the focus point... My tolerance is 3px only (and it’s still broke, as you may know), and Snap to Point is off.
You see me trying to start a path and continue it as a continuation of the glyph’s diagonal, but fail, until I zoom in enough. Still, I fail :)
Yes, I have construction and transform options enabled for smart guides. Disabling them does not solve this.An error occurred while saving the comment 17 again. Ah, right, Smart guides should be on! Hm. Then problem 24 again. So you can’t change option for glyph snapping, but highlighting anchors still makes it snap, even when glyph snapping is off :(
Still you should create a switch right in the Type panel to enable the snapping without going to View.... I know about global-snap-place (can’t wait), but it won’t solve this completely too.An error occurred while saving the comment 27. When a proximity guide is drawn, please place small 'x' sign not at the edge of the bounds, but at a point this guide is based on. Like if it’s build on an overshoot of an 'o' glyph, place the x-mark on this particular overshoot’s tangent point. If there are many points contributing to the guide, mark the closest one.
An error occurred while saving the comment 26. Not aligned to zero, Ai lies, you can clearly see the guide is tilted. It also happens in similar cases when no text involved (the second image).
An error occurred while saving the comment 25. For some reason smart guides that are based on glyph point are not green, but magenta. I assume it’s a bug, actually. It would be some much more useful if these stay green all the time, when at least one thing participating in glyph related. And it would be so much better, if Ai could draw green and magenta simultaneously: glyph based guide in green and normal in magenta, intersecting, for example.
An error occurred while saving the comment 24. Highlight Anchor option (Prefs: Selection & Anchor Display) also works for text, when Snap to Glyph option is on, but all other snaps (smart and to point) are off. This relates to a bug (rather an issue) when you don’t want Ai to snap to point, but because of this highlight option you still have it! I emailed about this and demoed it to Varun.
I’m worried it might cause problems.
Also, the 'edge' of green highlighted anchor is 2px wide, while normal is only 1. Not a bug, just an observation. I kind of love it! :)An error occurred while saving the comment 23. Play button in 'how to' blank document is not locked :)
An error occurred while saving the comment 22. See the image.
Also 'Feedback' button doesn’t work.
And if you have a new document about snapping to glyph, the Learn will open another one if I run 'See how again'. Also, the document name is blank and I’m not sure it would not be confusing.An error occurred while saving the comment Aviansh, 24.4 RC3, with 'fixed' error messages. It runs :)
17. I see new icons there, good. They look better than those you screenshoted. But they are all grayed out, while the option in View is on! Turning is on and off doesn’t help.
18. (i) icon in the panel leads to https://helpx.adobe.com/illustrator/using/snap-to-glyph.html and gives 404.
19. Icons need more differences (btw I love height options icons for the same reason): two of them say 'Ax'. If you change the first (not second) one to, say, 'Az', it would be easier to locate 'x-height'. I think that 'Ab' could be even better ('baseline').
20. I like the 'proximity' word, good! The icon though, doesn’t provide enough info. There’s no guide at A's top, or guides near overshoots (of course, they would be too similar to baseline and x-height there at this scale).
21. New Learn is cool. Slide 3 though can make you think that this relates to angular case, while it’s not.An error occurred while saving the comment 16. Angular guides does not work. Great idea! If it would work better then Smart Guides work now — it would be massive.
See, I can move the point on a live extension (unless the adjacent points have no handles — I emailed about this at sharewithai), but if I try to place a new point on the extension, Ai would give me nothing. ...and I'm not sure that you can do it with angular guides for glyphs, because the result I saw in the PR feature demo had not angles matched.
It also won’t help if I hover the pen over the bottom point to make rubber band 'notice' it (sometimes it helps for other cases). I know that snapping requires big rework, but now angular guides does show nothing for me, even captions I saw in demo.An error occurred while saving the comment 15. Beta got updated. No new icons yet. Hover hints doesn’t provide info for all the options.
An error occurred while saving the comment 14. When dragging a multi-line text along the vertical axis, its baselines and x-height lines are shown (which is great), but only the current one and not all others, which would help to choose the line to snap to.
An error occurred while saving the comment 13. Ai won’t snap to the glyph point located exactly on the 'x-height' line, when corresponding options are on
An error occurred while saving the comment 12. In 24.3.0.52 Ai still display green guides and performs snapping to glyphs when the option is turned off
An error occurred while saving the comment 11. When I disable 'Tight Bounds' option, snapping to baselines (it's on) in multi-line point text stops working.
An error occurred while saving the comment 10. It is still active when I disable the option (View > Snap to Glyph(s)). I have Smart guides on and Snap to point off, and it still snaps to tightbounds and glyph points.
An error occurred while saving the comment Oh, yes! My precious feature is finally here! I'm so glad that A) you picked it up, B) it works as intended from the get go, C) you managed to solve all the possible issues we discussed. You even picked the color for guides I proposed, green!
First impression:
1. You should definitely think about Snapping panel, that would combine all snaps options we would now have.
2. You should make hover hints when you hold cursor over the options. It's great that you decided to have Secondary lines as a separate option, but it's not self-explanatory. I kind of knew what this could be, but still had to spent 15 seconds testing it.
3. If you have secondaries and points off (and all other options on), and you have a line 'Lorem', starting with a capital, you won't be able to snap to the x-height!
4. What it you highlight glyph points with green too? This would indicate their 'liveness' more, because otherwise users can think that they have their text accidentally outlined.
5. Secondary lines should have a caption and indicate a point that is used for snapping. For example, if you have it snapping to 's' top arc, place a cross at the top point of it (right now cross is placed on the left edge)
6. Sometimes green captions overlay default magenta ones (usually it's 'tightbound'+'intersect'). I think you could omit one in these cases, but not sure which one.
7. I think secondaries should be off by default, and points on (but with green captions!). When you have points on, you just don't need secondaries that much — of course, in case when the font have proper tangent points.
8. Tightbound applies to every line — great!
9. Well, I think that you can leave magenta as magenta for glyph points, but try to highlight a glyph still in green (yes, I remember that I voted against it, it's just in case if you cant' make green for points work)
That's all for now. I will continue to test it. Again, my thanks to the team for making it real. I'm so proud of it! Along with the height options this would be a thing that really makes changes.
But don't forget about bugs ;) -
2 votes
An error occurred while saving the comment Looks like GPU issue.
-
2 votes
An error occurred while saving the comment Aha, makes more sense.
Still, a screenshot, please :)
If you can attach a photo of you screen, it would help too.An error occurred while saving the comment Please make a screenshot and attach it in the comments.
It might be no Ai’s fault, but you monitor physical calibration.
Anyway, a proof is welcome. -
1 vote
This often happens when we open Preferences and accidentally press Up or Down arrow key. The very first field focused in the dialog is Keyboard Increment value, and pressing an arrow makes it either zero (which turns into the smallest allowed value of 0.0001) or 2 (if you had 1).
Open Preferences and change the value back.
An error occurred while saving the comment You are welcome, Dru.
I have no idea how it can be changed by itself and I almost never met complains about it — but 3-4 I have already. Thank you for reporting, it helps.An error occurred while saving the comment Dru, please check 2 things:
1. What keyboard increment value do you have set in Preferences
2. Do you have Snap to grid enabled?
There’s a bug when these two interfere. -
2 votes
An error occurred while saving the comment What export command are you using? with what settings exactly?
Does it happen on all the files or one only?
Does the restart help?
Can you share the file you are having, both original and exported here or via the sharewithai@adobe.com (with the copy of this report)? -
2 votes
An error occurred while saving the comment Herbie, what command do you use to paste?
Ctrl+V will just pastes in the middle of your viewport — all the time, no exclusions.
Paste in Front/back. on the other hand, paste using your current artboard’s coordinates, so it matters which one is active. For example, if you copy stuff form the big artboard and paste it on the smaller one — it will result the copy to show up beyond the smaller one and maybe outside you current view. -
2 votes
An error occurred while saving the comment Jlo, this is odd.
Does it stays when you restart the Ai?
Does it work fine when you copy with Alt+Drag?
Does it differ when you copy/paste between documents or in one only? -
2 votes
An error occurred while saving the comment Yeah, hello again. Same thing — disable 'Use preview bounds' option.
-
6 votes
If this happens for you, please check the 'Use Preview Bounds' in Preferences > General. When it’s enabled, Ai will treat strokes and effects as a part of the object’s bounds.
An error occurred while saving the comment Please check the 'Use Preview Bounds' in Preferences: General.
When it’s on, Ai will treat strokes and effects as a part of the object.
:)
If disabling it won’t help — message back, please.An error occurred while saving the comment Check your Align/Snap to Pixel Grid options int top right corner of Control panel
An error occurred while saving the comment You should sent the file to 'sharewithai@adobe.com' and describe exactly what you do.
-
4 votes
An error occurred while saving the comment Edit similar object seems to not a proper thing to use for aligning at all. As you point out, changing positions in this mode leads to simultaneous shift of all the copies.
Still I can’t get what is exactly you are going to solve with these.
So please, Daan, if you had a video or a GIF recorded, showing what your intentions are, this could help more than a text. -
1 vote
This happens if the colorization method for a brush is chosen to be just None.
Changing it to be Tints or any other form the dropdown in the brush’s options solves the problem.
An error occurred while saving the comment Yolanda, please check if you have the colorization method in brush options set to anything other than None.
-
2 votes
An error occurred while saving the comment Tiago, this can be caused by GPU.
Try to update your video card driver and/or disable GPU preview to see if it’s related. -
1 vote
An error occurred while saving the comment Does it happen only with this file or any other too?
If everything is affected, then Try to reset you preferences first: https://astutegraphics.com/support/tutorials-and-troubleshooting/resetting-illustrator-preferences
If it doesn’t help and/or only this file is affected, please share it. -
1 vote
An error occurred while saving the comment Charles, please check video driver, this I know could cause such bugs.
-
1 vote
An error occurred while saving the comment Shane, as a temporary fix try to disable GPU preview.
If it helps, please send the file (packaged, with the image) to the sharewithai@adobe.com, titled 'GPU issue'. -
1 vote
An error occurred while saving the comment On Windows, Shift+Scroll is fast vertical and Shift+Ctrl+Scroll is fast horizontal. Sadly, can’t test it on Mac.
-
10 votes
This issue is resolved in Big Sur (macOS 11) public release
An error occurred while saving the comment If you disable GPU — does it stay?
-
1 vote
An error occurred while saving the comment Suzzie, share a screenshot?
-
1 vote
An error occurred while saving the comment Allowing direct selection to edit parts that outside of clipping paths, however, could definitely cause a lot of frustration when mistreated. I can think of a lot of cases this would **** me off :) Still, I think that this can be very useful.
Alos, I believe that this could work well with this thing:
https://illustrator.uservoice.com/forums/333657-illustrator-feature-requests/suggestions/41001730-don-t-display-clipped-paths-in-outline-view-optionAs for the second part, I believe this is the original intention and not a strict 'bug'. But I agree completely that it’s not how it should work and I have a request for fixing it:
https://illustrator.uservoice.com/forums/601447-illustrator-bugs/suggestions/40073080-clicking-filled-clipping-path-doesn-t-select-it
It has surprisingly little votes.
This is odd.
Select Same Stroke Weight does work for me (except for complex appearance, but that is a different story)
You should move the lines you can’t select in a separate files, check if the bug still happens, and then email it to sharewithai@adobe.com, preferably with the recording of how it does work for you.
Or you can attach these here in a comment.