Export persona filenames: User variables don't show up anywhere?

[Stokestack]

I set up a template for GUI buttons, with versions of a button in all of its potential states. In my Export persona, I have each as a slice, exporting all three necessary resolutions for iOS.

But I don't see any way of setting a base filename, and then appending the slice name to it. The Export persona lets you set up a "user variable" for export filenames... but then doesn't show it anywhere except where you defined it. Is this a bug?

 

[v_kyr]

You can place a cursor and type text above (before/between/after) placed vars.

And any path keeps it's own user var settings now, independent from the others, aka they seem not to be shared among entries.

[Stokestack]

Thanks, but that only changes the one name. Try it. If you type something in there, it won't be reflected in any other output filenames.

That's the point of a user variable: You can change its value in one place, and all of the output filenames that include the variable will change accordingly. At least... that's how it should work. It appears to be broken in Designer, because the user variable isn't made available to you after you define it.

In my screen shot above, I created a variable called "base_name" and set it to be "native". If I insert base_name at the beginning of every output name field, every output filename start with "native". Next time, if I change my design and want to give all of the outputs a different name, I should just be able to change base_name to "something else", and all the output filenames will start with "something else."

[v_kyr]

16 minutes ago, Stokestack said:

Thanks, but that only changes the one name. Try it. If you type something in there, it won't be reflected in any other output filenames.

I know that's what I said above in the last sentence. - BTW in previous versions setting own user vars in the bottom table was buggy and nearly impossible. Looks like they reworked that, though the table of user vars actually isn't shared as an object between other slice output filename entries. So you would now have to rework every slice output entry on it's own.

[Stokestack]

6 minutes ago, v_kyr said:

So you would now have to rework every slice output entry on it's own.

Which totally defeats the purpose of having a variable... and defeats the purpose of this whole dialog. I can't believe that's the intentional design.

[v_kyr]

I can imagine they fixed the buggy behavior from previous versions and maybe didn't got the shared interoperability part in time, so left that off. - You can file in a bug report in order to get some response here.

[Stokestack]

I did post this in the feedback/bug-report forum too, and the moderator there confirms that this is a known defect. Thanks.