i think fl.controls components can useful if want things way built. however, i'm running serious usability issue whenever need have different "versions" of symbol contains same component.
for example, have question view has 9 rows of radio buttons in (each row inside symbol manages state of radio buttons). question view symbol in library in question templates>questiontype>thistypeofquestionview. demo, want version of that has 6 rows of radio buttons. copy question view symbol instructions>questiontype.
this has added folder called questiontemplates>questiontype thistypeofquestionview in it, along new copy of radiobuttonrowsymbol , folders copies of component assets needed radiobutton (and guaranteed not work, since can have 1 asset same linkage id). rename question view demothistypeofquestionview , move root of instructions>questiontype. fixing copy of radiobuttonrowsymbol easy--i drop copy of questiontemplates on questiontemplates.
but repair process component assets involves opening every folder in nonfunctional component assets copy lowest level , dropping contents onto appropriate "real" component assets folder , selecting "replace" each time. tedious , fraught error.
is there setting somewhere can select leaves pointers assets in copied symbols pointing same place, while still keeping base class definitions in place?
i can't sure believe because skinning important part of components, duplication necessary evil. believe favored slight file size increase , skin customization.
the problem runs deep in code completion. you'd expect completion when creating copy of object it's not sophisticated enough because of dynamic , custom nature of code. in same way can provide multiple custom skins duplicated components can provide custom class variants doesn't inflect completion because never know user intends. believe limit of that, not knowing don't care customize duplicates.
More discussions in Adobe Animate CC - General
adobe
Comments
Post a Comment