Skip to content

Derek

My feedback

5 results found

  1. 5 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)
    Derek shared this idea  · 
  2. 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)
    Derek shared this idea  · 
  3. 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)
    Derek shared this idea  · 
  4. 80 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)
    FIXED  ·  Abhinav Kaushik responded

    Hello All,

    Thank you for your patience all this while.
    This issue is now fixed in the latest update (Id 14.0.1) of InDesign CC.
    If you are unable to see the update notification yet, open the menu (three dots) from the top-right of Creative Cloud desktop application and click on ‘Check For App Updates’.

    Once the update button is shown against InDesign CC, click on the button to update your InDesign to Id 14.0.1 for the fix of the issue.
    Do let us know in the comments, if you face any problem with the new update.

    List of fixed issues can be found at: helpx.adobe.com/indesign/kb/fixed-issues.html

    Regards,
    InDesign Team

    An error occurred while saving the comment
    Derek commented  · 

    The beta is working well but I often reopen the program to find that the window does not conform to my previous placement. This build however seems to be remembering custom workspaces, just not always window sizing.

    An error occurred while saving the comment
    Derek commented  · 

    This appears to have fixed the issue. I am continuing to test. However I am finding that when I reopen InDesign it does not preserve my window settings which can be highly frustrating. I have custom workspaces saved and it seems to default at times back to 'Essentials'.

    The other issue is that after installing the Beta, I found last night that the CC Installation Manager had a new download of InDesign, but it wasn't an update, rather it stated 'Install'. I did this and it reverted to the shipping version which lost my custom workspaces. I then reinstalled the Beta and as stated upon reopening I still have my custom workspaces but they do not open after closing Indesign and opening a new session again. Once I begin the new session I must chose my desired workspace. Please fix. Thank you.

    An error occurred while saving the comment
    Derek commented  · 

    Please fix this as if the control panel is not docked this fix does not work consistently. This is a serious bug.

    Derek supported this idea  · 
  5. 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
    Derek commented  · 

    It appears that upon reboot of my laptop this issue is now resolved. Perhaps it was a holdover from the 2017 version. It was exhibiting this issue directly after install and first start up of Indesign, this morning it Preview on CPU is working normally. It can be turned on or off without issue.

    An error occurred while saving the comment
    Derek commented  · 

    Is anyone else seeing this issue? It's rather bothersome.

    Derek shared this idea  · 

Feedback and Knowledge Base