Unfortunately it looks like the 2016-05-25 build of pdlork loses previous path in Finder - so when you open pdlork for the first time, and press cmd-o, it boots up in either Documents, or inside the pd-package (inside the app). then when I maneuver into my PD-folder and load a patch, the next cmd-o (open) will again misplace where I was before.
Are there plans to make user-selected-folders sticky?
also, are there plans to make it so that the user can define a default folder that cmd-o(open) automatically opens to?
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
However, you're right that when you launch PD, it starts up in the application folder (which is somewhere inside /Applications/Pd-l2ork* for technical reasons) and that is also the folder you get when first invoking Open. This bugs me as well. I think that the initial Open folder should be the user's home directory, as it is with vanilla and Pd-extended.
Better yet, on OSX PD should actually set its cwd to $HOME after startup is complete (this is also what happens on Linux if you launch the app from a desktop icon). @jwilkes, are there any technical reasons preventing that?
On a related note, the folder icon in the help browser opens / (the root folder) on OSX and then in ~/Documents afterwards, this is also wrong. It should open the app.nw/doc folder instead.
Hi @aggraef, I was able to get the pipelines build (although when opening the build - it still says it is 20160625 - so the disk image filename versioning is not perfect.
however, yes, now when I click on Open, after loading a file - the previous folder is remembered, which is real swell. :)
ouch, i just forcequit the newest build of pdlork and got bumped back to app.nw -folder by Finder on OSX. However, when I had loaded something previously, pdlork remembered which folder I was at.
@aggraef
one detail that might be helpful for OSX -- it appears that before the Finder-window goes to the correct folder, it seems to go through the process of:
Open Finder-window (when user taps on Open)
Briefly show that you are in Documents folder (even though the user is somewhere else)
Then switch to showing the "previous folder" (i.e. where the user expected to be shown "to" in the first place).
So it seems that a Finder-window is opened with "the defaults", and then switched to somewhere else.
It works - there's no doubt about it - but it feels quite strange that the Finder-window does not automatically open in the right folder.
I.e. if the user was loading a file on the Desktop, the Finder-window that opens first shows Documents for the briefest of time, then changes to the Desktop-folder, instead of directly opening in the Desktop-folder.
I hope this description somehow makes sense. It's really minor, (rreeaallllyy minor), but ykwim.
The problem here is that pwd is getting set from two different places-- set_vars of index.js and from gui_set_cwd in s_inter.c.
I'm not sure I even realized this. Anyway, I'm not sure what the best way to fix it is. Of course I can do a "darwin" check inside gui_set_cwd. But then if someone wants to build and install Purr Data on OSX without using an App bundle, this would break.
@jwilkes Your recent commit resolves the issue with the initial Open path on OSX, thanks! However, the folder icon in the help browser still opens in / rather than app.nw/doc, I'll open a separate issue for that.