.Drewt
My feedback
10 results found
-
15 votes
We have confirmation from multiple users that copy paste crash issue is resolved after updating to latest MS Windows Defender security intelligence update - 1.435.148.
Request everyone in this thread to update to the latest MS Windows Defender security intelligence update - 1.435.148 and share if this resolved this issue.
An error occurred while saving the comment .Drewt
supported this idea
·
An error occurred while saving the comment .Drewt
commented
I had been running 29.7 without any issues. When the update for 29.7.1 appeared I updated. It worked fine for a couple of days, but now Illustrator crashes whenever I use Ctrl+C or Edit > Copy. It only appears to be when I copy objects on the artboard. If I copy a value in a field e.g. a colour hex value from the colour panel, it doesn't crash. I tried reverting to the previous version that was working for me (29.7), but it crashed with Ctrl+C. I have also tried rolling back to 28.7.8, but it too now crashes. Although an object can be copied with alt-click + drag, this is by no means a practical or efficient workaround, nor does it cater for all Ctrl+C use-cases . For me, Illustrator is practically unusable at the moment.
-
41 votes.Drewt
supported this idea
·
-
73 votes.Drewt
supported this idea
·
-
139 votes
Starting with Beta 29.9.0.36 it’s now possible to lock the objects on artboard basis from the Artboards panel, using a new Lock column, similar to one the Layers panel has.
How it works:
- In the Artboards panel, select one or more artboards and click Lock.
- All objects on those artboards lock automatically.
- To edit a specific object, simply unlock it from the Layers panel.
Give it a try and let us know what you think. Your feedback helps the team to shape what comes next.
An error occurred while saving the comment .Drewt
commented
Here's how I'm picturing it. Similar to the layers window, it has a visibility (eye) icon and a lock (padlock) icon that can be toggled on and off. In the attached example:
- Artboard 1 is visible and unlocked, artwork can be edited
- Artboard 2 is hidden (invisible) and is also locked. The locked state has no bearing in this case as invisible means both the artboard and associated artwork is hidden. However, if the artboard were made visible by clicking the eye icon column, the artboard and artwork would become visible again, but would be locked so that the artwork could not be edited.
- Artboard 3 is visible and locked. The artwork can be seen, but cannot be edited.
- Artboard 4, like artboard 1, is visible and editable. In this case it is the currently selected artboard which is being actively worked on by the user..Drewt
supported this idea
·
-
27 votes.Drewt
supported this idea
·
-
43 votes.Drewt
supported this idea
·
-
52 votes
Beta 30.0.0.21 now offers an option to show the numbers and names for the artboards for any tool chosen.
You can disable this in Preferences > Selection & Anchor Display, with Show Artboard name on canvas option.
Yo can also double-click the name and rename the artboard directly on canvas.
This is a very first draft of the feature. Please try this build and share your impressions in comments, to help to guide the development.
.Drewt
supported this idea
·
-
51 votes.Drewt
supported this idea
·
-
84 votes.Drewt
supported this idea
·
-
93 votes
We’ve been working on this feature, and it’s now available in the latest Illustrator beta. We encourage you to try it out and share your valuable feedback with us.
.Drewt
supported this idea
·
The 1.435.148 Defender Antivirus update has resolved the issue for me.
What hasn't been resolved:
- Why was this an issue in the first place? None of the other Adobe flagship products had the issue. What is it that Illustrator passes to the clipboard that Defender didn't like?
- What is Adobe doing to prevent this from happening again?
- Two weeks with minimal communication to the user community is unacceptable. We should have been given daily updates that we could at least pass on to our clients. How will Adobe address this in future?
- Many users like me spent a significant number of hours trying to resolve, test and workaround the issue, losing a lot of time and delaying deliverables for our clients. How will this be addressed?