Skip to content

Jason Burnett

My feedback

35 results found

  1. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi,

    Thanks for reporting this issue, Illustrator team really appreciate this.

    Unfortunately we are unable to reproduce this issue in house.
    Can you help the Illustrator team to isolate this issue further so that we can nail this down?
    1)Kindly provide small video describing the issue , Test file(Via File→Package) & Font with which you are able to reproduce this issue and share with us at ShareWithAI@adobe.com in a Zip file.

    Please mention the title of this issue as the subject of the mail.

    Thanks and Regards
    Ankit Goyal
    Illustrator Team

    An error occurred while saving the comment
    Jason Burnett commented  · 

    Here's what I have found: When I am looking for just the right apostrophe or comma or ligature or something, I often scroll through the GLyuph panel and look for resources in various fonts that I can use to get the look that I am going for.

    When Illustrator reaches a font that doesn't have the core letters defined (symbol fonts, icon fonts, font-alternates), rather than skipping the font it can't render or rendering the character set that it CAN render, Illustrator just stops. This is really annoying.

    Some examples would be Fork Awesome, a port of an old Font Awesome icon font. When I scroll through and get to Fork Awesome, it stops scrolling until I manually select a different font that it can display.

    Oddly enough, clicking on the font will display the font with no problems, it's just when scrolling using the down arrow that the next font won't display and the scrolling stops.

    Hope this clarifies the problem.

    Jason Burnett shared this idea  · 
  2. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett supported this idea  · 
  3. 48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jason Burnett commented  · 

    Is it at all possible that the reason for the delay on some of these issues is that an entirely new interface is b being developed that is more like the web or iPad version? That would explain the lack of response on some of these issues.

    Keeping my fingers crossed.

    An error occurred while saving the comment
    Jason Burnett commented  · 

    Why isn't this fixed?

    This post is 2 years old and it still doesn't work. There are 34 upvotes, what does it take to get this resolved? Could we at least get some acknowledgment that this is a priority?

    I am losing all faith in Illustrator. You are so busy adding new "features" or previewing new technologies that you leave us with a faulty application. There is no excuse for this. It should have been fixed two years ago. It's a legitimate bug.

    Please do something about it.

    Anyone reading this, join me in starting a campaign to get people to come to this site and upvote this. Lots of people have this problem and it's a legitimate bug. If we push the votes to the top, maybe they will actually address this issue. It's been two years and this is ridiculous. Contact everyone you know. I'll post on Discord and Reddit and hopefully we can get some traction. Thanks.

    An error occurred while saving the comment
    Jason Burnett commented  · 

    Shees, every time I said cursor, I meant pointer. That's rough.

    Regardless, reading through the comments made be realize something. It has to do with Windows Magnification. I am using a 4k Ultra Wide monitor at 200% magnification. This is making the area that activates the rotate feature bigger than it should be. Somehow, they didn't compensate for the magnification in Windows.

    When I drag Illustrator to a different monitor, the problem goes away.

    Jason Burnett supported this idea  · 
  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett shared this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett shared this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett shared this idea  · 
  7. 45 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett supported this idea  · 
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Jason Burnett commented  · 

    My consistent problem with this concept is that it is constantly in the way. I have to move it out of my way at least a dozen times every hour. And hopefully you are tracking the number of clicks it receives to tell if it is more useful than in the way. In other words, if you register a click event every time someone interacts with your floating context panel, you can separate the number of moves from the number of useful functions clicked. If people are having to move it more than use it or if people aren't using it, that's valuable feedback.

    I would much prefer a collapsible side panel with all of the tool options as well as a portion of it for the most common predicted tasks. Sure, I'd have to mouse a little farther, but at least I am not losing my focus constantly having to drop what I was doing and move the thing so I can access the anchor points it's obscuring.

  9. 72 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    It is now obvious the issue was not fixed fully. The developers are aware of it now. Let’s hope it will be fixed soon enough.

    If you have a solid order of steps which reproduce this behavior, share them in comments, because only some machines are affected. Please help the team to isolate it.

    An error occurred while saving the comment
    Jason Burnett commented  · 

    This is actually a big problem with all panel values in Illustrator. There are standards that we comne to rely on when "selecting and focusing" input fields that are not being honored by illustrator.

    For example, WHEN FOCUSING AN INPUT FIELD, select the entire contents of the field every time. DO NOT EVER INSERT THE INSERTION POINT where the person clicked, for example. ALWAYS SELECT ALL when activating a field.

    This is true if you tab into the field, click to activate it, if it is activated by a third party plugin. ALWAYS SELECT THE ENTIRE CONTENTS of the field when activating a field.

    I cannot tell you how many times a day I click the X field and type in my value, press tab, and have to deal with a modal dialog box telling me that it didn't understand. THIS IS NEVER A GOOD IDEA.

    Either that or if I enter 45 and tab, it sometimes puts 45 in the middle of the previous X value. Now my artwork is at 3459px because it was 39px and I clicked it to make 45, but Illustrator inserted my cursor in the middle rather than selecting the content.

    This is also a problem with units. Whatever the default units, keep them unless I specify differently. But if I don't specify units, you can rest assured that whatever I enter into that field will be using the default units.

    This is probably my biggest complaint (or second biggest) with Illustrator. Devs need to implement industry standards for INPUT field UX. If I want to insert my insertion point in the middle of a value, I'll click a second time once the field is FOCUSED. That's how it is supposed to be done.

    Jason Burnett supported this idea  · 
  10. 115 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jason Burnett commented  · 

    All of Adobe products suffer from focus issues. But Illustrator is really bad when it comes to things like layers. The fact that you have a layers panel that you can select layers (without selecting the corresponding objects on the layers) is confusing and counter-intuitive. Usually, you click a layer to activate the content on that layer.

    Adobe could fix both problems by introducing a "focus" feature that allowed to you "lock" in your focus on something.. So If I am editing a large tree with lots of fruits and leaves in the way, but I wan to focus on the tree branches, I would click a button on the control bar once I had the branch selected. This would force my focus to be on the branch.

    With focus locked, selecting anchor points or handles would be a piece of cake. There would be no doubt that when you clicked anywhere near an anchor or handle, it would select the anchor or handle. You might even be able to allow multiple handles to be simultaneously selected when focused.

    You could alt-click or right-click or click the toggle lock button in the control panel to return to mormal.

    In our tree example, once you had the complicated branch selected, then you focused your selection, you could easily move even normally hidden anchors and handles because Illustrator would KNOW for sure that is what you intended. Otherwise, how could it tell that you wanted to grab that tiny handle and not the object in front of it?

    You could even allow for people to grab and manipulate the handle bars. Instead of having to grab a handle, clicking anywhere on the bar that the handle was attached to would allow you to maintain the angle while moving the curve.

    When in focused mode, the screen could be surrounded in Yellow, like when in isolation mode. Lots of things then would become possible. LIke offset dragging where you select your points then click and drag somewhere on your artboard to move the points relative and offset from your current position. (Like 3D apps occasionally do).

    An error occurred while saving the comment
    Jason Burnett commented  · 

    I think this may have to do with screen magnification on my PC. I often can't grab a handlebar or a point on a path. Often, when trying to change the width of height of something, the cursor changes to indicate width or height, but the item rotates instead. The latest version eliminated all of these abilities without the transform tool active--which sucks. I think it is because I have a 38" curved monitor that I have to run at 175% to read the content on it. I don't think Illustrator has got that part figured out yet.

    Jason Burnett supported this idea  · 
  11. 160 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We have the fix available in the latest release. Please update Illustrator using Adobe Creative Cloud application to the latest build for version Illustrator CC 22.1.
    Please refer to our knowledge base FAQhttps://illustrator.uservoice.com/knowledgebase/articles/1844590 if you face difficulty in update.
    Or get in touch with us at any of the other support channels – https://helpx.adobe.com/support.html

    Warm Regards,
    Ashutosh Chaturvedi | Sr. Quality Engineering Manager – Illustrator
    Adobe. Make It an Experience.

    Jason Burnett supported this idea  · 
  12. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett shared this idea  · 
  13. 48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett supported this idea  · 
  14. 82 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett supported this idea  · 
  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett shared this idea  · 
  16. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett supported this idea  · 
  17. 46 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jason Burnett commented  · 

    There are standards used throughout computing that inform how field values work and Illustrator screws this up terribly.

    When a field is not in focus, clicking on the field or the field value brings the field and value into focus. This automatically should select the entire user-editable contents of the field value. This allows you to click and type a new value to change the value.

    Illustrator instead changes the cursor to an insertion point when hovering over a field value. Clicking in the field value, places the insertion point at the location the pointer was at. If you then type the value you want, you will NEVER get the result that you want. This is not okay.

    Illustrator requires you to click in a field (places the insertion point in the middle of the field value), then click again at the beginning of the field value (which is super problematic when the field value contents are bigger than the field input space) and drag to the end of the field value BEFORE you can enter your new value. Most often, you have to select part of the field value, delete it and then press the del or delete key until you get the full contents gone so you can enter your new value.

    And what is more infuriating is when you enter a value with units, for example, without looking you press tab to advance to the next field and get a modal dialog box stopping you from doing anything else just to tell you that 300em4px is not a valid value. This is infuriating.

    And this is problematic through Illustrator's numerical field value selection. If you have just entered one value and press tab, the next field value should be selected by default. Here, Illustrator handles the focusing of the field with autoselecting the field value correctly. But that's problematic if you just went through the reprogramming to convince yourself that because of Illustrator's failure to understand the focus event, you need to manually select the field contents, now you are doing extra steps you don't need to do. Unbelievable that an app could ***** it up no matter how it is used.

    Current Problem: Illustrator places the insertion point on a newly focused field instead of selecting the entire contents, only when selecting from the mouse or touch interface. It should, instead, follow the same procedure that it uses to focus a field when tabbing from one field to another: Select the entire contents of the field value when focusing.

    Jason Burnett supported this idea  · 
    An error occurred while saving the comment
    Jason Burnett commented  · 

    There are certain default behaviors that one becomes used to when using a computer and Adobe appears to have completely disregarded this with respect to manually entering values! Please fix this serious bug.

    When clicking on any modifiable value field, a single click should select the entire contents of the field by default. If I click on the width field in the Illustrator top bar, I should be able to simply type a width and hit tab or enter to apply. THIS IS NOT HOW IT WORKS.

    If I see that my width is only off by a small amount that is easily stepped, I should be able to use the up and down arrows (either in the field or on the keyboard) to increment or decrement my value by the next closest whole number in either direction. THIS WORKS CORRECTLY, but only by automatically selecting the entire value THE WAY IT SHOULD WHENEVER YOU CLICK A FIELD VALUE.

    If I click a field value and realize that I want to just change the last two numbers or perhaps the current units, I SHOULD CLICK THE FIELD A SECOND TIME WHERE I WANT TO INSERT MY CURSOR AND THE CURSOR SHOULD GO THERE, DESELECTING THE VALUE. Clicking and Dragging across a value should operate in this same way, CLICKHOLD where you want to insert the cursor and drag to SELECT THE VALUE TO CHANGE. This makes sense because the CLICK-HOLD action is really CLICK CLICK-DRAG.

    Currently, I click a field value and think that I can quickly change the value to 50px, so I type 50px and press ENTER (only to get an error that 1050px pt is not a valid value--a total bust to my workflow. So I click the field again and have to use CTRL-A to select the entire contents of the field in order to type the new value. THIS SHOULD BE BY DEFAULT.

    CLICKING A FIELD, like tabbing into the field, SELECTS THE ENTIRE CONTENTS. CLICKING A SECOND TIME PLACES THE CURSOR AND DESELECTS CONTENT. CLICK AND HOLD OR CLICK+DRAG SHOULD OPERATE LIKE DOUBLECLICK

    This is common sense and Adobe is the only software package on the market that handles this in this peculiar way. Please fix it.

    P.S. And here's the deal: when I enter a value and press tab, if I haven't explicitly declared units, use the previously assigned units. Don't complain that I didn't have the right units. I can't tell you how many times I have entered 50% in the width field just to be told that 2150%80px is not a valid entry.

    P.P.S. It is terribly inappropriate and completely unhelpful to click an item and be told that it is 100% wide....That makes no sense. Percentages are always relative in context. If you say it's 100% wide, you have to say relative to what? It's original size? the window size? It's parent size? Width and heights should not be presented in % by default. Always use the current units (px, cm, mm, etc). and if you wan to add a "transformed" width or height (to the TRANSFORM PANEL), you need a Context field that indicates what the percentage is applied to. This would be great if you wanted to make a shape with 4 identical columns...you would draw the parent shape, then enter isolation mode to add 4 columns, each of which was 25% wide 100% tall given the context of their PARENT. THen later, when the item is broken apart, the height and width are only available in the current preferred units, not %.

  19. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jason Burnett commented  · 

    If I can downgrade to the previous version, I could show you in a heartbeat. Apparently in the latest version they have removed all functionality that lets you modify a selected element without having to change tools.

    Up until this very last update, when you selected an item, the bounding box would be displayed. Clicking on any of the bounding box handles would allow you to transform the size. Clicking in the middle would allow you to drag the element to reposition and clicking close to the handles would change the pointer to the rotate pointer, allowing you to rotate the element.

    Now, that is gone entirely. There is no way to transform the element, especially rotate the element when you just have it selected with either arrow tool. Now, you have to select the transform tool to apply any changes.

    And what is frustrating about the transform tool is that you can't select a new element easily. You have to use keyboard modifiers to select a new element or an additional element if the transform tool is selected.

    It's a HUGE change to the way Illustrator has worked for the last, what 20 years? Sure, I can get used to it, but it sucks.

    I believe that this is because they are unable to compensate for Windows 11 OS being scaled to 175% on a large 4k monitor. When I set the scaling to 100%, it used to work as expected. It was only when I increased the scaling so I could actually read the content on a 39" 4K monitor that the problem presented itself. This is a terrible approach to solving the problem.
    https://imgur.com/a/7WQOrLa

    An error occurred while saving the comment
    Jason Burnett commented  · 

    If I can downgrade to the previous version, I could show you in a heartbeat. Apparently in the latest version they have removed all functionality that lets you modify a selected element without having to change tools.

    Up until this very last update, when you selected an item, the bounding box would be displayed. Clicking on any of the bounding box handles would allow you to transform the size. Clicking in the middle would allow you to drag the element to reposition and clicking close to the handles would change the pointer to the rotate pointer, allowing you to rotate the element.

    Now, that is gone entirely. There is no way to transform the element, especially rotate the element when you just have it selected with either arrow tool. Now, you have to select the transform tool to apply any changes.

    And what is frustrating about the transform tool is that you can't select a new element easily. You have to use keyboard modifiers to select a new element or an additional element if the transform tool is selected.

    It's a HUGE change to the way Illustrator has worked for the last, what 20 years? Sure, I can get used to it, but it sucks.

    I believe that this is because they are unable to compensate for Windows 11 OS being scaled to 175% on a large 4k monitor. When I set the scaling to 100%, it used to work as expected. It was only when I increased the scaling so I could actually read the content on a 39" 4K monitor that the problem presented itself. This is a terrible approach to solving the problem.

    Jason Burnett shared this idea  · 
  20. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Burnett shared this idea  · 
← Previous 1

Feedback and Knowledge Base