[Bf-committers] Win32 paths

[Bill Baxter]

Actually, I spoke too soon.  Removing the trailing slash does fix the 
problem with finding Python scripts, but it does not fix the YFexport 
problem.  Console output is:
------
    Starting scene conversion.
    Scene conversion done.
    Could not open input file
    Could not execute yafray. Is it in path?
------

--bb

Bill Baxter wrote:

> Ah yes.  That seems to fix it.  Thanks Nathan.  I guess if it can't be 
> fixed at this point it should be noted in big bold letters in the 
> release notes. The fact that the file chooser returns paths with 
> trailing slashes kind of exacerbates the problem.
>
> --bb
>
> Nathan Letwory wrote:
>
>> These problems are because of the trailing slashes in the pathnames.
>>
>> /Nathan
>>
>> Bill Baxter wrote:
>>
>>> Load and save of prefs is working fine with Simon's checkins from 
>>> earlier.
>>> But there are a few other path problems I'm having (and have had 
>>> since I started checking out CVS versions a few days back):
>>>
>>> 1) If I set the YFexport path, I get this message:
>>> Yafray found at : C:\PROGRA~1\YafRay\
>>> 2) I don't get any scripts in my menu.  I set the Python: dir to 
>>> someplace with annotated scripts, but when I click the little 
>>> "re-evaluate" icon I just get the popup: "err invalid scripts dir: 
>>> check console".  But the console doesn't say anything.  Here's an 
>>> example of the annotation in one of the files in that directory:
>>>
>>> This is on WinXP.
>>>
>>> --bb
>>
>>
>>
>>
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> http://www.blender.org/mailman/listinfo/bf-committers
>
>
>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers