Sergey
My feedback
28 results found
-
56 votesSergey supported this idea ·
-
16 votesSergey supported this idea ·
-
12 votesSergey supported this idea ·
An error occurred while saving the comment -
20 votesSergey supported this idea ·
-
22 votesSergey supported this idea ·
-
10 votesSergey supported this idea ·
-
10 votes
Hi Everyone,
We have fixed this bug in our latest release – v 28.2.0 which is available worldwide now. Thanks for your patience on this.
You can update to the latest release using Creative Cloud desktop App: https://helpx.adobe.com/in/creative-cloud/help/creative-cloud-updates.html
Sergey supported this idea · -
724 votes
It is not as straightforward as it may sound :) We have been working to take advantage of threads and other hardware such as GPU/Video RAM in places where it can make a higher impact. We are prioritizing areas that are slow instead of making a generic change and destabilizing the product. Product stability is the top priority for us and we have been consistently trying to improve it. We want to move with caution and make changes without compromising on the quality. Hope this helps.
Sergey supported this idea · -
735 votesSergey supported this idea ·
-
8 votesSergey supported this idea ·
-
6 votes
An error occurred while saving the comment Sergey commentedIt turned out that the bug of not saving strokeDashOffset value also affects only negative values of this parameter.
Sergey supported this idea ·An error occurred while saving the comment Sergey commentedIt seems that the strokeDashOffset parameter is not even saved in the ai source file, because when you reopen it, strokeDashOffset value is again zero.
So it's not just a fragile property. It is a ghost property: you can look at it, but not use it, because it disappears when you try to capture it.
-
21 votesSergey supported this idea ·
-
20 votes
I am happy to share that we have fixed this bug in our latest release – 24.2.0 which is available worldwide now.
Going forward, our goal is to fix as many top User-Voice bugs as possible and as frequently as possible. Given the nature of the fixes, some of the bugs will take a longer time to fix, but we are on it.
You can update to the latest release using Creative Cloud desktop App: https://helpx.adobe.com/in/creative-cloud/help/creative-cloud-updates.html
Thank you for all the feedback. Keep it coming!
Sergey supported this idea · -
26 votes
Hi Paul,
We would need these files to reproduce this issue. Can you please share the same on my mail ID: anish@adobe.com
Thanks
AnishSergey supported this idea · -
27 votesSergey supported this idea ·
-
36 votes
Hi All,
Thanks for reporting this issue and sorry for the inconvenience caused. We are able to reproduce this issue at our end and it is currently under review.
Thanks
Anish Kumar
Illustrator TeamSergey supported this idea · -
45 votesSergey supported this idea ·
-
177 votes
The team again asks for help with this issue, since there are not specific steps they can try to reproduce it — the nature of the bug is random.
If you are a Windows user, the next time you spot a missing or a duplicated number in Artboards panel, please follow these instructions below.
1. Open Task Manager
2. In Details tab, locate 'Illustrator.exe'
3. Right click it and choose 'Create dump file'
4. Wait until the dumping process is complete and click 'Open file location' button
5. Find 'Illustrator.dmp' (sorting files by date helps) and compress it with any archiving utility
6. Upload the archive to a file hosting service of your choice and sent the link for download to sharewithai@adobe.com. Please use the subject 'Artboards numbering bug dump'
This will help provide necessary clues to locate the source of the problem. If you are a Mac user —…
Sergey supported this idea · -
27 votes
I am glad to update that this issue was fixed in 23.1 release.
Thank you for all the feedback.
Sergey supported this idea · -
28 votesSergey supported this idea ·
Same thing.