Auto layout is mostly great, but has its issues. You create an auto layout it reflows automatically based on what's visible. But I wish the "bounding box" for the auto layout would shrink to what's currently visible, so that other items — in my case in a "parent" auto layout — could reflow too.

In the image, "rule settings" is an auto layout inside another auto layout. When "Notate for SOC" is active, it shows a hidden group. But when it's hidden it still takes up space and affects the bounding box.

Would love it if hidden items in normal groups didn't affect the bounding box unless they're actually visible too.

There is a workaround using a cropped group, but that gets a bit messy.

The top is Illustrator, bottom UXPin. The icon is a compound path, which is how we need them for the web. If I release the compound path it will display (mostly) correct but UXPin doesn't respect the path cap (round, etc). Quite frustrating. Am I doing something wrong?

I need a way to expire ("turn off") old links I've sent out that contain outdated design. Is there a workaround or any plan for this type of feature?

Here is the same SVG file in UXPin, on a web page, and in Illustrator (where it was drawn). The only problem is the way it's displaying in UXPin. It's connecting the open paths, and it shouldn't be. Any ideas how I can fix this?

The attached video shows my regular frustration working with the color palette. It closes every time you apply a color. So, when you need to apply many, there's a lot of clicking and scrolling. These colors happen to be closer to the top, so it doesn't even show the most extreme situation. But this is still very tedious.

While on the topic… Having to hover to get the values, when they used to be exposed by default, makes things much harder, imo.

It usually doesn't make much sense to have random dates. If you selected a date and the quick replicate (or whatever it's called) spit out sequential dates, now that would be very useful. 

If you're like me, you send out tons of links to different iterations of different features/products. This inevitably leads to questions about the latest versions. I try to post them in the JIRA task and I keep a changelog that everyone has access to, but you know people don't like to read or do any investigation themselves. LOL

Have you come up with a solid way to deal with this?

…do you piece it out into several prototypes, one per section or feature? This is how I currently do it and was curious how the single prototype approach works out. Seems like it may get bloated and slow.

When I export to HTML and open in Chrome, console complains that it can't find data/fonts.css and everything displays in Arial. A code comment says this CSS is auto-generated. Is it? If this CSS was present, would it display the fonts correctly?

If you have a group of elements that act as a link or trigger for an interaction, the cursor will jump from default to pointer as it hovers over the elements and the space between them.

For example, I have an icon and text element that I want to act as one link. before. mov shows the issue. after. mov shows the improvement.

The solution is to select the group and check Crop selected content.