Skip to content

Settings and activity

1 result found

  1. 713 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
    Mo Baba commented  · 

    I have found a work around to this situation and it works quite well!

    After making the instance local (which still relies on going to the original Master and therefore doesn't solve the problem we are facing), I used CMD+Shift+K and the instance became a master. I am now able to use it as I want!

    But this process can only be executed in a new file. If done in the same file as the original Master, CMD+Shift+K will go to that original Master instead of creating a new, independent Master.

    I made screenshots in the attached.

    Please let me know if this works for you too.

    Mo Baba supported this idea  · 
    An error occurred while saving the comment
    Mo Baba commented  · 

    The 'Use it as a new master component' will actually be very helpful. I have edited master components affecting their instances when that was not the purpose. I want to be able to turn some instances into masters so that edits on the 1st master will not affect the instances.