On 01/25/2013 04:21 PM, me.grimm wrote:
plugins can be loaded from the user-set path because I didn't see a reason why someone would want to do that.
that would be so one might have a different gui look for each of their patchs. or could distribute a gui-plug specific to their patch with their patches, etc.
in my case im using the gui-plugs to make my patch look like some absrtacted, glitch, unusable mess... but then if i leave it in the standerd path every patch i would open would be like that there for if i could [declare] the path to the gui-plug then i wouldn't have to worry about it. only that one patch would have those properties....
Hmm, that would be tricky for Pd to make a GUI-plugin only apply to a single patch, but you could program that in GUI plugin itself. Use [wm stackorder .] to get the list of open windows, then go thru the list and check [wm title ], then compare that to the patchname you want to affect. Then use that to make a canvas id, and only use that canvasid to change things. ROughtly like:
foreach mytoplevel [wm stackorder .] { if {[regsub {mypatchname} [wm title $mytoplevel]]} { set tkcanvas [tkcanvas_name $mytoplevel] break } }
Now $tkcanvas is the canvas that you want. I didn't try the above code, it might have errors, but that's the idea. You can also do that in a patch itself with [hcs/window_name] and [hcs/canvas_name].
.hc
As for the prefs pane for loading libs at startup, that is bad behavior that should be discouraged. Libs should be loaded in the patch using [import] or [declare -lib].
i agree hence the "in patch" gui-plugin loading....
hmmmm
m
On Fri, Jan 25, 2013 at 4:01 PM, Hans-Christoph Steiner hans@at.or.at wrote:
On 01/25/2013 03:31 PM, Jonathan Wilkes wrote:
----- Original Message -----
From: me.grimm megrimm@gmail.com To: pd_list Listserve pd-list@iem.at Cc: Sent: Friday, January 25, 2013 9:25 AM Subject: [PD] Loading Gui-Plugin in a Directory Other than in Standard Path
i tried declare like so:
[declare -stdpath /Users/megrimm/Desktop]
but that didn't work.
is there anyway to load gui plugins other than dropping them in ~/Library/Pd , etc ?
I don't know.
Hans-- is there a translation page that shows the new way to do everything in Pd-extended that used to be done through the path and startup dialogs?
I guess first of all-- is it possible to do everything on the current release that could be done on the last, such as the behavior in question above?
You can set paths in the preferences still. I never tested whether GUI plugins can be loaded from the user-set path because I didn't see a reason why someone would want to do that.
As for the prefs pane for loading libs at startup, that is bad behavior that should be discouraged. Libs should be loaded in the patch using [import] or [declare -lib].
.hc
-Jonathan
m
-- ____________________ m.e.grimm | m.f.a | ed.m. megrimm@gmail.com _________________________________
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list