[oXygen-user] Feature Request: Variables for Path Components When Building Result Locations in Scenarios

[Peter West]

On 8/02/2014 10:14 am, Eliot Kimber wrote:
> But I don't necessarily want the full relative path from the project root.
> In fact, I would almost never want it.
>
> Cheers,
>
> E.
Notice that my reply has been deleted.  That seems to be a result of 
having the entire message converted to base64 encoding. What is 
MacOutlook up to?

Anyway, the ${rppd} or ${rdppd} macro would be generally useful.

Form what you've said, it seems that the ${env(VARNAME)} option won't do 
it for you, because you would have to set the variable for each 
directory level you are processing.

The quick and dirty way to get programmability would be to do the 
conversion, then provide for a sell-out with a given set of ENVVARs, and 
a known file name in which the shell could return the path of the 
transformed file, so that Oxygen would be aware of where things ended up.

-- 
Peter West
"For what does it profit a man if he gains the whole world and loses or forfeits himself?"