Re: Forcing absolute paths

[Adam Ferrall <aferrall(at)alumni.cmu.edu>]

I seem to get the correct result (in this case at least) when I have 
already inspected the RenderOptions PPG.  If I run these commands on a 
new scene before inspecting the PPG i get relative paths for both 
results, but if I open the PPG and then run these commands I get the 
expected relative and then absolute paths for the commands.  It seems 
like something is done in the PPG logic for this scenario on initiation 
of the PPG, but I haven't been able to run down just what yet.  Maybe 
you know what's being done in this process Halfdan to explain the 
different results?  Thanks.

-Adam

kim aldis wrote:

> No you don't. Try it.
>
>  
>
> > -----Original Message-----
> > From: owner-xsi(at)Softimage.COM 
> > [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Halfdan Ingvarsson
> > Sent: 06 July 2005 20:23
> > To: XSI(at)Softimage.COM
> > Subject: RE: Forcing absolute paths
> >
> >
> > If you run this script with a new scene:
> >
> > LogMessage GetValue( 
> > "Passes.Default_Pass.RenderOptions.ImageFileName" )  
> > LogMessage GetValue( 
> > "Passes.Default_Pass.RenderOptions.ImageFilePath" )
> >
> > You'll get this:
> >
> > 'INFO : Render_Pictures\Default_Pass_Render.#.pic
> > 'INFO : C:\db\Render_Pictures\Default_Pass_Render.#.pic
> >
> >    
>
>
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
> unsubscribe xsi
>
>  

---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi