Sergey Osokin
My feedback
226 results found
-
78 votes
As you probably know, Illustrator today allows to change this behavior with a dedicated option in Preferences > Selection & Anchor Display section.
However, it’s not that accessible, especially when you are already move and copy your artboards.
If you wish this option to be more exposed, consider upvoting this request: Display Move Locked and Hidden Artwork with Artboard option in Control panel and Properties while using Artboard tool / mode
Sergey Osokin
supported this idea
·
-
13 votesSergey Osokin
supported this idea
·
-
4 votesSergey Osokin
supported this idea
·
-
5 votesSergey Osokin
supported this idea
·
-
72 votes
The fix is pushed to the stable release 29.0.1.192
Sergey Osokin
supported this idea
·
-
6 votesSergey Osokin
supported this idea
·
-
41 votes
It turns out the problem is fixed only partially in 26.3.1, only for some users, and the performance remains slow when grid is rendered with lines or dots in Outline mode. This applies to zooming, panning and ghosting of objects being moved.
Please help the team by providing your specs and answers to these questions:
1. Does it work fine with grid as dots in Preivew / Outline mode?
2. Does it differ from grid as lines in these modes?
3. What is slow for you exactly? How severe?
4. Is there a difference if you disable 'Grids In Back' option?
5. What are you lines/subdivisions settings?
And any other related feedback is appreciated. Let's track it down and get this really fixed.
An error occurred while saving the comment Sergey Osokin
supported this idea
·
-
4 votesSergey Osokin
supported this idea
·
-
3 votesSergey Osokin
supported this idea
·
-
8 votesSergey Osokin
supported this idea
·
-
7 votesSergey Osokin
supported this idea
·
-
40 votes
Illustrator Beta 29.2.10 now supports Nonbreaking space (U+00A0).
It can also be added with Type > Insert WhiteSpace Character > Nonbreaking Space command.
Please try this build and see if it works for you as expected.
My sincere congratulations to everyone. This symbol means a lot!
Sergey Osokin
supported this idea
·
-
10 votesSergey Osokin
supported this idea
·
-
6 votesSergey Osokin
supported this idea
·
-
16 votes
We have fixed this issue in 29.0 and 28.7.2 releases.
Sergey Osokin
supported this idea
·
-
59 votes
Hi everyone! Thank you for your feedback so far.
As we make progress, we wanted to hear your thoughts regarding the intended functionality of this solution. We are sharing two scenarios forproposed behavior of this functionality, please review these and let us know your feedback:
Scenario #1: The area calculation will only consider the path geometry of an object and not include the stroke weight as part of the computed area. To calculate the area of the stroke, the object can be Expanded so that a separate compound path is created for the stroke.
Scenario #2: Appearance-altering effects (e.g., Drop Shadows, Gaussian Blurs) that do not modify the underlying path geometry will not influence the area calculation. We will continue to calculate the area of the actual closed path.
We have also attached a visual reference for these scenarios to this post. Please let us know your thoughts!
Sergey Osokin
supported this idea
·
-
3 votes
The team has started working on this request. As a first step they want to understand the requirements correctly and build the right feature set based on the feedback gathered.
If you are willing to discuss area calculation in a call session, block a time slot here: https://outlook.office.com/bookwithme/user/c1b7ecea1cbd42a2a7068cfeb7861bdd@adobe.com/meetingtype/Fn8tXNebh0eyv4xTnvQ-3Q2?anonymous&ep=mlink
Sergey Osokin
supported this idea
·
-
3 votes
The team has started working on this request. As a first step they want to understand the requirements correctly and build the right feature set based on the feedback gathered.
If you are willing to discuss area calculation in a call session, block a time slot here: https://outlook.office.com/bookwithme/user/c1b7ecea1cbd42a2a7068cfeb7861bdd@adobe.com/meetingtype/Fn8tXNebh0eyv4xTnvQ-3Q2?anonymous&ep=mlink
Sergey Osokin
supported this idea
·
-
14 votes
The team has started working on this request. As a first step they want to understand the requirements correctly and build the right feature set based on the feedback gathered.
If you are willing to discuss area calculation in a call session, block a time slot here: https://outlook.office.com/bookwithme/user/c1b7ecea1cbd42a2a7068cfeb7861bdd@adobe.com/meetingtype/Fn8tXNebh0eyv4xTnvQ-3Q2?anonymous&ep=mlink
Sergey Osokin
supported this idea
·
-
13 votesSergey Osokin
supported this idea
·
.png){kind=link}
MacOS Catalina 10.15.7, GPU GeForce GTX780M 4GB, Samsung SSD 860 EVO, CPU Intel i5 3.1 GHz, memory 16 GB
What I found on Illustrator v26.4.1, v27.6.1:
1) Grids in Back (on) + Show Grid + View using GPU + User Interface Canvas Color: White >> performance degradation
2) Option Grids in Back (off) + Show Grid + View using GPU + User Interface Canvas Color: White >> performance good
3) Option Grids in Back (on) + Hide Grid + View using GPU + User Interface Canvas Color: White >> performance good
4) Option Grid in Back (on) + Show Grid + View using CPU + User Interface Canvas
Color: White >> performance good
5) Option Grids in Back (on) + Show Grid + View using GPU + User Interface Canvas Color: Match Brightness >> performance good
That is, the main performance hit on my spec is on the GPU when Grids in Back and Canvas Color: White are enabled.
==================================================
An even stranger observation is when a grid of lines in the background reduces performance. Setup: Grid in background (on) + Show grid + View using GPU + User interface canvas color: White.
1) I open Preferences and change the grid style to dots.
2) I close Preferences. A grid of dots is rendered on the screen.
3) I open Preferences and change the grid style back to lines.
4) I close Preferences. The grid of lines renders on the screen... And now performance is normal! While the document is open.
Restarted Illustrator. The trick of changing grid styles doesn't work anymore. Performance remains poor.