On Tue, 2019-01-15 at 14:08 -0200, Alexandre Torres Porres wrote:
> 
> 
> Em ter, 15 de jan de 2019 às 13:56, Roman Haefeli <reduz...@gmail.com
> > escreveu:
> > 
> > I can currently only test on Linux, but yes it works. However, when
> > banging [openpanel] initially, it doesn't open in Pd's start
> > location,
> > but in its "Home" which happens to be ~/Documents/Pd in my version
> > of
> > Pd (0.49.1).
> 
> that's actually 0.49-0, right? 49.1 is only for mac

0.49.1 is what Pd shows. I compiled it myself, so maybe I'm using a
version where the most recent changes affect only macOS.

> > I don't know what the start location is on platforms where you
> > double-
> > click an icon to launch the application. But you can easily figure
> > that
> > out by sending [symbol .( to [openpanel]. 
> 
> Sending a "symbol ." here in the latest macOS and Pd opens the root
> of HD 
>  
> > From there, relative paths should work. I guess, they do so also on
> > macOS and on Windows once you
> > know where your starting point is. 
> 
> So, a bang opens ~/Documents/Pd, but no relative paths work from
> there!

I try to make myself more clear: [bang ( opens  what I called `Pd's
Home`. In order to use relative paths you send it [symbol .( and this
path is what I called Pd's start location. Relative paths work only
relative to what [symbol .( shows, NOT to what [bang( shows.


> So it seems like a bug for mac, and also, we want the behaviour to be
> relative to the patch's path, right? At least when sending it "symbol
> ./"

It's not a bug, unless you say, that paths are not even working
relative to  what [symbol .( shows. You haven't said that yet. You only
said, that it is not working relative to what [bang ( shows.

Roman

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Reply via email to