Skip to content

Feature request about a problem after swapping instance

A greate idea thank you for bring this out. I've decided to adapt my a couple of master components and I realised that swapping instances broke the plugin's special layer name structure.After that I tried to "hack" that situation by grouping layer which I wanted to alter by the plugin.

For example assume that there is a master component that has |leftIcon + TextType + rightIcon| leftIcon and rightIcon: instances of icon set components thus they can be swapped TextType: an instance among 3 text type components(type01, type02, type03). Only one of them will be used.

normaly we should make layer names for them like below (leftIcon) + [textType.TextType_type01][textType.TextType_type02][textType.TextType_type03] + (rightIcon)|

if I swap an instance above component's variable structure is broken. so I tried to get all of them in seperated groups

(leftIcon) ------Group --leftIcon ------instance

(textType) ------Group --textType/type01 ------instance

(rightIcon) ------Group --rightIcon ------instance

so this plugin now control group containers and I could swap instances. but after that I realised that this usage will increase document complexity and may be it coused some unwanted autolayout problems. So I drop to use this plugin for now and I wanted to ask you that is that possible to prevent this usage? without grouping can we use this nice plugin in the future?

thanks a lot