Re: Load extensions from abstraction folder?
IOhannes m zmoelnig <[email protected]>
| Newsgroups | gmane.comp.multimedia.puredata.general |
|---|---|
| Message-ID | <[email protected]> |
On 11/13/24 09:21, adam johnson wrote:
> And you can maybe use plugin-dispatch-receiver for a vanilla solution,
> something like:
>
> [loadbang]
> |
> [plugin-dispatch start-plugin args
> |
> [s pd]
>
> then in the plugin itself
>
> proc start-plugin (args) {
> source this-plugin.tcl
> }
that looks like a hen-egg problem.
in order to be able to call "plugin-dispatch", the gui-plugin has to
register with the plugin-dispatcher... and in order to do that, it has
to be loaded first (in which case you've already solved the problem).
or to put differently: "plugin-dispatch" is not a way to send arbitrary
commands to the GUI.
also note that you probably shouldn't "source" the tcl-code directly,
but instead use the 'load_plugin_script' proc (which adds some safety
around the actual sourcing)
gmasdr
IOhannes
---
[email protected] - the Pure Data mailinglist
https://lists.iem.at/hyperkitty/list/[email protected]/message/L7BNPLR56TFUVKH2SVZ6QLFKOFWEL33B/
To unsubscribe send an email to [email protected] mailing list
UNSUBSCRIBE and account-management -> https://lists.iem.at/
OpenPGP_signature.asc
(application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmc0gRMFAwAAAAAACgkQtlAZxH96Nviv zg/9HrB7jMEdD0vBIqViS04jpn5Ud2s7XmTizy0f4uV1v5SdEA4/K8P7n8uxyoL4QfGAU67ID6gp MLDb0a8XD3DmJAa62/ro5odeVccCUeocrieRXIZRYXovMpLfqOD17i9hVhQWNmhEm7TnDpPSCyhb DzBuDc62kTCx9OXxTpBVkDhzr5aXEOvdwqPaiL49aQ+xVpUWr1GR/1mbQNjBCKPYaVv+VxLINRXR NetSMdUd/y37FeFcJPL/mn5FVLE2J8mKaEdO2Xg0hyj70GmC1DKhbP6Aw8zhbm5zl67nHtKRWAct Mu2xHjudTrsXFP1mJYSc61PIiuZT1UC4F92GrCfLHjvIMy59wjza0IGB8kqZTjtZtj108RbVaiPK 1UdSwqgMqlbbXukfahJxjMYkc1c+yX+qttgziqwAo3q/Mkt6Epf75R/K0ybiY0HBZVy6UC9aKI30 kZAS2UOe9EjC4vaAbkY21ds1JtM4KdgsLT+xWVObr2eDjfQGJmmDv8MUmm/hCIVr+Va7IXJrHO9z SKyFN+z4M0bDETV20aBV7G5Rdfg56Ni4P68D32fuZuanxSHZUWpSqEMA5OBcQBQOKHPj0AqDMySp VqotV4KP9VJiWq581pk5XYkhvgdVL1Qfn7/Xrkcny7fLUWNJCi2nfCbJgTVzNHaPaajXqSke/Huj xyg= =yQ2J -----END PGP SIGNATURE-----