this patch adds a gui-preferences system, right now for recent files only.
recently opened files are written in the user-app-config directory (i.e. ~/.config/pure-data/recentfiles.conf on linux) and read when pd launches.
this was tested on linux and osx only (I don't have access to a win32 machine).
see the following related threads:
http://www.mail-archive.com/pd-dev@iem.at/msg09330.html
http://www.mail-archive.com/pd-dev@iem.at/msg09351.html
Anonymous
recentfiles support patch
This is looking good, I just have a couple comments:
- I think you should manually edit pkgIndex.tcl. the script made a bunch of changes, that are not really relevant and might affect other things. You just need to add a single line for pd_guiprefs.tcl
- preferences on Mac OS X are stored in ~/Library/Preferences rather than ~/Library/Application Support/pure-data. Ideally, this patch would also use the terminal tool 'defaults read' and 'defaults write' to create a proper Mac OS X .plist preferences file. Its not hard to do, you can see how Pd currently does it in pd/src/s_file.c. Windows needs to use the registry, that's even easier because Tcl has the built -in 'registry' command.
new patch for gui prefs
I finally found the time to make a new patch:
- added support for osx preferences and windows registry
- new file is now added to recentfiles if it's saved
- better error handling
- better doc (pd_guiprefs)
- bugfix 3192731 (http://sourceforge.net/tracker/?func=detail&aid=3192731&group_id=55736&atid=478070)
the patch was tested on archlinux, ubuntu10.10 and osx 10.5.8
on windows I could only test the registry stuff in a tclsh prompt, please test !
I couldn't apply this to 0.43.. (failed on po/Makefile.am - I couldn't figure
out why).
new patch that applies on current HEAD
it didn't apply because of some changes in po/Makefile.am since this patch was submitted.
I just uploaded an updated patch.
thanks... worked that time.
I forgot to include 2 small fixes in the patch, new one uploaded
added small fixes
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).