Is anyone else using Auto Layout in their components?
I find it slightly annoying that elements get forced to have a fixed width when making something a component.
Auto layout has some really useful use cases for moving things in the right way with the right padding when changing instances of text for example. Once this becomes a component the width is forced to fixed making it pretty pointless for being a component.
I wondered if anyone else has come across this issue?
Yes, I have. Once an element has been converted into a component it loses all of its previously designated padding and auto layout.
its very discouraging and makes using components unappealing. I wish I could use a true atomic approach in making a uxpin library.
I couldn't agree more. Auto layout and components are the two most powerful features UI tools offer. They are at their best when used on the same element. It's frustrating that UXPin does not allow these features to work together. Because I have to use either a component or auto layout, my design library is fragile and cannot be scaled effectively.
Currently, the auto-layout elements are indeed limited when converted to components, which is related to disabled auto-size functionality in components. You can only break and rebuild the component to override the design. But of course, we want to improve that in the future and provide a better experience with this feature!
For now, if you would like to have a fully functional element I’d recommend trying Merge, Its Patterns act as a standard UXPin library, but it allows you to go beyond atoms and basic components into more complex ones. If you are interested in a demo, let us know!
Just started experimenting with Auto Layout and got something functioning perfectly after spending tons of time understanding how to use Auto Layout. Sure enough, when I needed it as a component, I lost all value that Auto Layout brought. Pretty disappointing. Hopefully there is some new function coming to Auto Layout / Components so we can actually utilize this functionality. It should be standardized to ensure that new functions will always work with Components as most of us are building interfaces with a design system / pattern library of some sort. There are just some really weird things that UXPin can't do and constantly make me scratch my head.