Skip to content

Anonymous

My feedback

1 result found

  1. 76 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
    Anonymous commented  · 

    So I spoke too soon. I posted below about #2 working but it ONLY works if the X field doesn't glitch on the tab first. I just typed in the X field and it glitched (changed to different number after entering intended number and pressing tab) after tabbing before I could even go to the Y field. So have to take it back and say I couldn't consistently get this to work with the solution outlined.

    An error occurred while saving the comment
    Anonymous commented  · 

    #2 works well for me too if waiting at least 1-2 seconds after pressing tab when entering the X field but in essence it's like telling us to type slower. I guess this solution is do-able but it forces a change in habit by being more conscious in giving that extra pause between tabs. For me personally, that will take awhile for me to get used to and make it a habit. What do others think?

    I feel it addresses the symptom but being that this was not an issue in versions before 2016, may not be tackling the root cause.

    An error occurred while saving the comment
    Anonymous commented  · 

    Hi admin -
    I've emailed the video and file used in the video. This is still an on-going issue. And yes, as Anonymous from July 15 commented, this started happening and later versions, I want to say, starting at around CC 2016. Previously, this was never an issue. And to Anonymous from April 16, I doubt decimals have anything to do with it. This glitch happens when whole numbers are entered plenty of time as much as decimal numbers.

    Sorry about the video access. I think I've fixed the permissions *crosses fingers*:

    https://drive.google.com/file/d/1F2L2KobgMMRO5DUsvDV_YwJ0GqX3dhO_/view?usp=sharing

    An error occurred while saving the comment
    Anonymous commented  · 

    Hi, thanks for addressing this and apologies that it's taking me awhile. Recorded many videos when it didn't happen and when I did, the transform panel wasn't captured in the video. Finally got everything I wanted in the video. Video shows that I'm trying to center the text on an 18" x 36" artboard. You can see in the transform panel I am trying to center it at 18" on the X/horizontal axis with the anchor point at the center. It jumps to 27" which is a completely random number to me. The glitch in this video happens often and also when trying to align an object (usually a rectangle the same size as the artboard) to X: 0 / Y: 0 (with left corner anchored), the object will move in to the X-coordinate to 0 but not to 0 in the Y-coordinate and I have to deselect the object, re-select it and input the Y coordinate again for the object to finally also move in the Y direction. This also happens on my Mac computer.

    Let me know if there is other information I can provide.

    Link to Video:
    https://drive.google.com/open?id=1F2L2KobgMMRO5DUsvDV_YwJ0GqX3dhO_

    Anonymous shared this idea  · 

Feedback and Knowledge Base