justin

i have been working on transferring some max 4 patches to max 5 and have come across a problem. The absolutepath object in max 4.63 provides path information with a "/" character at the end of the path, whilst the max 5 version doesnt - is this a bug or modified functionality?

max 4 version - "macintosh HD:/blabla/blabla/"

max 5 version - "macintosh HD:/blabla/blabla"

This breaks an abstraction i commonly use to load files, which i could easily upgrade for max 5, but i thought i'd flag this up in case it was a bug...

to demonstrate the problem:
max 4 version - "macintosh HD:/blabla/blabla/"
max 5 version - "macintosh HD:/blabla/blabla"

absolutepath-object-in-max-5

Quote: justin wrote on Wed, 02 July 2008 06:45

----------------------------------------------------

> The absolutepath object in max 4.63 provides path information with a "/" character at the end of the path, whilst the max 5 version doesnt - is this a bug or modified functionality?

> max 4 version - "macintosh HD:/blabla/blabla/"

> max 5 version - "macintosh HD:/blabla/blabla"

Having an extra / won't hurt anything. So you can use /blabla//filename or even /blabla///filename to reference /blabla/filename

If you change your abstraction to append the extra slash, that should work in both versions of Max.

It does seem unintentional that this behavior would have changed...

Quote: justin wrote on Wed, 02 July 2008 06:45
----------------------------------------------------
> The absolutepath object in max 4.63 provides path information with a "/" character at the end of the path, whilst the max 5 version doesnt - is this a bug or modified functionality?
>
> to demonstrate the problem:
> max 4 version - "macintosh HD:/blabla/blabla/"
> max 5 version - "macintosh HD:/blabla/blabla"
>

It does seem unintentional that this behavior would have changed...


absolutepath object in max 5