rename AD added slices inside main slice feature request for AD 2

[kat]

 

I always rename main slices like Stirner_550x550 but can't rename slices inside Stirner_550x550 that I can't rename. Feature request for the next AD upgrade please

 

[GarryP]

Unless I’ve misunderstood your requirements, you can already do this my creating User Variables in the dialog which pops up when you click the ‘inner slice’ name and then dragging them to the Path Components area – see attached image.

It could be implemented better – deleting an existing user variable doesn’t clear it from the path components, changing the value of a variable doesn’t seem to do much, etc. – but it’s do-able.

[kat]

I tried dragging and adding. Nothing worked to rename secondary slices.

     

[GarryP]

For anyone reading this, I’ve attached a video showing how I can do it (I’m on Windows).

If that doesn’t work for you then you’ll need to tell us at which point in the process things stop working for you.

I think the problem you have is that you have forgotten to add the Value to the user variable.

[kat]

Resetting the name works, but it is tricky. Crashed my AD Mac a couple times before I could get the "thingy" (new name) value accepted and then drag "thingy" to the top.
Thank you — heroic solve, @GarryP.

 

[R C-R]

11 hours ago, GarryP said:

I think the problem you have is that you have forgotten to add the Value to the user variable.

You can just type the new name directly in the Path components section after removing the two variables there. There is no need to create & use a user variable & drag it into the Path.

Aside from that, on Macs (mine at least), there is no "x" to remove the variables, so just highlight them & use the delete key on the keyboard to remove them. Think of them like predefined text blocks that can be used with or without text typed into the path.

[R C-R]

@kat, I don't understand why you are having problems understanding this. Just try it: in the Path section at the top, remove both variables so the field is blank. Then type whatever you want there & that will become the new name.

[kat]

@R C-R, in the Path section at the top, remove both variables so the field is blank. Then type whatever you want there & that will become the new name.

I give you major credit for sticking with this. IT WORKED lol!

 

[R C-R]

Just now, kat said:

Double clicking in the path after removing tokens takes me right back to the values dialog box. 

Why are you doing that? After removing the 2 variable tokens just type your new name there at the top & click Done:

[kat]

1 hour ago, R C-R said:

Why are you doing that? After removing the 2 variable tokens just type your new name there at the top & click Done:

That's what I did

[R C-R]

1 minute ago, kat said:

That's what I did

I meant why did you double-click in the path after setting the name in the User variables? Like I said, you don't have to use a variable at all, user created or one of the predefined ones.

[GarryP]

I never thought of just typing the text into the Path Components field – that’s much easier.

Now I’m wondering why User Variables exist.

I can create a User Variable but it’s only available for use in the Slice I create it for.

So, if it’s only available for that Slice, and it can only be a single value (at any one time), which could just be typed in the Path Components field without faffing around with User Variables, what use are they?

[R C-R]

5 hours ago, GarryP said:

Now I’m wondering why User Variables exist.

Me too. It's like it is a feature that hasn't yet been fully developed, amost just a placeholder for something they intend to develop ater.

[carl123]

17 minutes ago, R C-R said:

Me too. It's like it is a feature that hasn't yet been fully developed, amost just a placeholder for something they intend to develop ater.

.

https://forum.affinity.serif.com/index.php?/topic/30155-user-variables-in-export-persona-path-components/&do=findComment&comment=166351

On 1/18/2017 at 11:21 AM, Ben said:

The variables are per object.  They were initially added to fulfil requirements for OSX and iOS Builder files (the variable is inserted into the output JSON files), but were done in a generic way to allow for future extensions to the output builders and inclusion in paths.

The idea is that you can generate a common path with placed variables, then you can copy and paste that path into another export item.  If you don't create that variable in your object then it will just be omitted from the path.  In order to insert one into a path, you do have to create it so that it can be drag-dropped into the path.

[kat]

1. Double clicking in main slice path works fine, but doesn't change sub slice paths.
2. To change sub slice paths I have to click in sub slice path which opens variable dialog box
3. in top box of variable dialog box I can change the name of the subslice. 
4. Despite the subslice name change when exporting I have to remove _2 which appears at the end of each exported subslice name.

Interesting topic. I'm learning — I hope. Thanks for contributing.

[GarryP]

Thanks for finding that old thread carl123.

I don’t understand the description by Ben but I’m not an Apple developer. (Even the bits I do understand don’t sound like they describe what the user can do, but this functionality is not for me so I don’t really have a problem with whether it works or not.)

It might be nice if this sort of thing was explained in the Help rather than users having to come to the forums to get answers.

[carl123]

My understanding is that it was a feature originally added for a different reason and was to be expanded on to give us the functionality that we were expecting by using variables but for some reason or other that expansion never went ahead so now it just puzzles most people that try to use it.

 

[GarryP]

10 minutes ago, carl123 said:

so now it just puzzles most people that try to use it

It certainly confused me.

I thought the way I showed kat to do it was the correct thing to be doing (it seemed reasonable to me at the time) but, as I’ve been subsequently told, I was just plain wrong.

I can’t find anything in the Help about it, but there’s a chance I missed it.

It might, perhaps, be nice if this sort of “Apple-developer-specific” functionality (it’s not the only one) was hidden by default with an option to expose it via Settings for the (very few?) users who want it.