Hmmm. yep, maybe the right policy would be simply to throw all of tk/tcl in Pd... I've been trying to avoid bloat but there's a real potential for lots of features breaking on Pcs if I try to hold to the policy of "only include what is being used".
I have to crank up my PC anyway to see about a bug report (asio4all seems not to work with 0.43) but probably won't be able to get to it this weekend - I have lots of bureaucrap awaiting me...
cheers Miller
On Sun, Apr 10, 2011 at 12:31:30PM -0400, Hans-Christoph Steiner wrote:
On Apr 7, 2011, at 3:13 AM, yvan volochine wrote:
On 04/06/2011 08:04 PM, Hans-Christoph Steiner wrote:
According to the Tcl/Tk 8.4 docs, it should be included. What if you just try to use 'registry' without the 'package require registry'?
it should but it's not. running tclsh84.exe shipped with pd-0.43 win binary:
package require registry
"Unknown command registry"
Miller, do you think you could add the libs that come with Tcl/Tk to your included version? There are two folders called 'reg1.2' and 'dde1.3' that should go into pd/lib directly, they come with Tcl/Tk in tcl/library/. These will also be needed to support making a double-clicked file open in the currently running instance of Pd. Really everything in tcl/library/ should be included so we have a full Tcl/Tk install.
Yvan, it should also be possible to include the 'reg1.2' folder in your plugin folder for making a plugin that people can use now. I think its just a matter of adding the local folder to the auto_path, so adding something like this to the plugin:
set auto_path [linsert $auto_path 0 \ [file join $::current_plugin_loadpath "openrecent-plugin"]
.hc
"Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev