AdminEgor Chistyakov
(Admin, Adobe Illustrator)
My feedback
7396 results found
-
6 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Bob, sorry, I don’t think I get it. Can you... illustrate the difference? Pun intended, but I really don’t understand what are you trying to say.
-
3 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
1 vote
An error occurred while saving the comment Window > New View, perhaps? To get at least two tabs with the same document opened, arranged in tiles, to see the artwork in both Preview and Outline modes, at different scales, and knowing which these scales are? But that is my guess, and the last time I worked in this split-view was like 7 years ago.
...and each tab still gets its own zoom level at the bottom-left corner anyway — though the inactive one is quite difficult to see.An error occurred while saving the comment Dalton, yeah, the simplification part I get clearly, and I personally like the feel the slimmed tabs give.
Sure, the zoom level is duplicated, but the current color and viewing mode are displayed only there. This is a shared behavior among major Adobe apps, and having the info there is crucial for a lot of users. I can’t say there are better places to put this info (except maybe in the underdeveloped Show bar at the bottom). Sure, some other apps just don’t show these constantly at all...It does not mean it can’t ever change, since it’s the universal design approach here — and I don’t say the idea is that bad — but making this single optional ticker that changes something global like this needs a lot of requests and serious arguments, other than just a mental feel.
I also imagine a number of 'help, I can’t see my color mode!' cries, for those who accidentaly turned it off... People often turn off the bounding box and come here to ask how they can have a resize option back! Again, it is a design problem with any modality, and it does not mean it can’t be made — but you asked about my thought process :)
Let’s see how many votes it gets.
An error occurred while saving the comment I can guess why, but I’d like to know your arguments, to check if we mean the same.
Also — if this option ever happen — do you have a specific place in mind you’d like to still be able to get this information from? -
3 votes
An error occurred while saving the comment Can you check if this works fine in the Beta version 27.6, please?
-
2 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
6 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
2 votes
This issue has been resolved.
An error occurred while saving the comment It feels like a problem with the UXP engine :/
I asked a developer to take a look at that, let’s see how it goes. -
17 votes
An error occurred while saving the comment Yep, Fredde, this seems like a reason behind it for sure.
Ai though just doesn’t provide a native way to reset the rotation of child paths (and actually it is not a proper solution, since we might need that data)
The naive solution is just to hit Pathfinder Add button, but it not just kills the data for children, but also moves the starting points and change directions sometimes (hence the arrowheads I applied). And sure one would have to repeat it for every child, which is again a better job for a script... and why use it then, when there is a better-but-not-perfect workaround? :)BTW, if you want to share the script you use to fix it, for others to use it, please put it directly in a comment, or rename the file to .txt, since UV blocks attaching .js/jsx files.
An error occurred while saving the comment Here is that basic test file and the recording
An error occurred while saving the comment I stripped one of the files to its bare minimum — two simple compound paths. One gets the bbox reset on rotation, the other does not.
No live shapes included.
Once you uncompound the problematic one, it’s clear the paths it has inside have different rotation angles.
Perhaps it has some sense, but not for us :(An error occurred while saving the comment Agree, cases differ. Let’s stick to 'Ai should allow to customize the behaviour' — and make it consistent across tools. What do you say about this approach? Is it OK to have all the tools behave the same for this, or does it make sense for some to always work with text or container?
An error occurred while saving the comment @Serge, the latest video of yours is actually an expected behaviour — 'at least for me'. This is why I use the bounding box only for area text transformations — Ai applies scaling and rotation with bbox to the path rather then the whole object, assuming this is what a user want to do.
Free Transform, Scale and Rotate, however, act on the whole object.To make these work just like the bbox does, you have to select the path of the area text, precisely, with a Group Selection toll (this is what I often do).
But if you add another object in a selection along with an area text, even the bbox starts to scale and rotate the whole text instead of a path of it.
'Expected' here means it has some logic behind it, and users can get familiarized about it... but I agree it can be treated differently. Like with a general option to Transform Area Text perhaps, which just toggle the behaviour? Note 'Area' here, because a point type text always gets scaled and rotated.
There are some requests about it as I recall, so you might want to search for them...
An error occurred while saving the comment @Dan, the problem is that the Illustrator codebase is huge. It can do a lot of stuff, it’s 30 years old, and the nature of bugs supposes to be unexpected even for developers. Just take a look at, say, a speedrun of Portal with developers’ comments — some tricks speedrunners use are just a mystery for devs and requires an explanation from those who plays Portal daily. Same deal here :) But this one indeed is very easy to reproduce... another problem is there are just too many easy-to-reproduce bugs, but solutions aren’t that easy to produce... and, ahem, Adobe seems to be more interested in buying other IPOs than maintaining their own.
An error occurred while saving the comment Yeah, thanks!
You know, looking at how it behaves (all is true) I don’t think I should want to use the bounding box :) I am just fine with hitting E to access Free Transform tool which is *almost* works like the bounding box, but easier to call and glitches less.
I use Scale, I use Rotate, some other tricks.
The only case for me to turn the BBox is to resize an area type text :)Regarding the issue... I made some experiments with these shapes.
I took a coin’s top face (a compound path) and rebuilt it: applied Exclude, Ungroup, Uncompound and Compound back. The result looks the same, but gets rotated with bbox just fine... until you rotate it with Rotate — this seems to reset the bbox immediately.
Once rotated with Rotate, the bbox always get reset on rotating a compound path. And if a group has a rotated-with-Rotate compound path in it, it has the same problem.What a nonsense.
Thank you all for raising this up!AdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
An error occurred while saving the comment Serge, Dan, everybody — can someone here share a test file for the developers to look at? 7 users, not a one file to dissect. It does not have to be the whole project you are working at, just that piece which glitches out!
I’d certainly provide it myself, if I had one, but I just don’t use bounding box at all, and have no idea if it gets reset or not. I will try to catch it though too.
An error occurred while saving the comment Serge, it doesn’t get reproduced for me anymore, with any tool, including Free Distort even.
Does it happen for you still? -
1 vote
An error occurred while saving the comment Yeah, Marcos, they rarely reply unless they have questions. Occasionally they do, so the channel works. Sadly, I can’t do much to force them to, and this way does not imply the are obliged to reply.
I’ll try to check if there is any info on this though.An error occurred while saving the comment Makes sense. But you say this happened some time ago, so you have a previous version of the file saved, am I getting this right? You open it and it works weird... can you send this file, the saved one? If it does not allow for itself to get packaged on opening, try to gather all the links and fonts used in it manually, zip it and share the archive. Without the files team can’t start investigating it really.
An error occurred while saving the comment Marcos, you can share this file with the team privately via sharewithai@adobe.com. Please package the document via File > Package to include all fonts and links, and also provide the exact steps to reproduce the problem, if possible (like which PDF preset or settings you use).
-
2 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
4 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
2 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
2 votes
An error occurred while saving the comment Just to clarify — whichever search location you choose in the functioning drop item list, the field itself still does not become focus-able, correct?
-
7 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
3 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
4 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
3 votesAdminEgor Chistyakov
(Admin, Adobe Illustrator)
supported this idea
·
-
1 vote
An error occurred while saving the comment Kira, toggling Overprint Preview basically disables GPU. I assume View > Preview on CPU does the same, right?
To help the team to investigate this, can you share the test file and your exact specs (OS version, GPU model, its driver’s version), along with the screenshots, to sharewithai@adobe.com? Please also mentions the link to this report for tracking purposes (https://illustrator.uservoice.com/forums/601447/suggestions/46559017)
-
2 votes
The problem got solved by enabling the bounding box back: View > Show Bounding Box (Cmd/Ctrl+Shift+B)
An error occurred while saving the comment Lorenzo, most probably you disabled the bounding box, accidentally, with a Cmd+Shift+B hotkey. Please try to press it again, or toggle it back via the menu — View > Show Bounding Box (somewhere in the middle).
This is a very common problem! Reply back if it works — or doesn’t. -
4 votes
An error occurred while saving the comment If possible — please try to remember as much details about the context of the crash: what were you trying to join, how complex were the appearances for these paths, were they on a same layer or not, etc. — anything to help to reproduce it as close to your case as possible.
Also — did you send the crash report, or you didn’t get the crash reporter dialog?
@Bob, ahh, so you refereeing to the iPad version! You should have clarified it right from the start.
Then I agree.