a [text] (and get its first line from your abs)
Inside the main patch, I use [text] to read constant values from a textfile. Then I could store them in containers like [symbol], [float], [list] in each abstractions but it seems (for me) not flexible. It does not allow to open a patch or an abstraction which needs thoses values. I can reload the textfile when the patch is opened but I don't like this design : when I reload the textfile I trigger values into the 2 patches.
My way now is a [text] loader of the same textfile into my main patches, called once at the startup.
The [pv] object from cyclone is a good choice, thanks for the tip. It just needs to be created in a parent level.
But if you only have to get its constant value (and not to modify it) then you could just call a shared abstraction in your abs, that would just send the symbol to an outlet?
Do you mean one [text] loader into each abstractions ?
Hello Jérôme,
Did you try to use a server with that value. And then use clients in your patches/abstractions to query this value to the server at startup ? I could be a possibility... ++
Jack
Le 06/01/2017 à 16:05, Jérôme Abel a écrit :
a [text] (and get its first line from your abs)
Inside the main patch, I use [text] to read constant values from a textfile. Then I could store them in containers like [symbol], [float], [list] in each abstractions but it seems (for me) not flexible. It does not allow to open a patch or an abstraction which needs thoses values. I can reload the textfile when the patch is opened but I don't like this design : when I reload the textfile I trigger values into the 2 patches.
My way now is a [text] loader of the same textfile into my main patches, called once at the startup.
The [pv] object from cyclone is a good choice, thanks for the tip. It just needs to be created in a parent level.
But if you only have to get its constant value (and not to modify it) then you could just call a shared abstraction in your abs, that would just send the symbol to an outlet?
Do you mean one [text] loader into each abstractions ?
Do you mean one [text] loader into each abstractions ?
I just meant loadbanging a symbol (or a message). e.g:
shared_symbol.pd:
[loadbang] | [symbol MySharedSymbol] | [outlet]
Then patches calling [shared_symbol] will get the symbol at load time.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-01-06 18:30 GMT+01:00 Jack jack@rybn.org:
Hello Jérôme,
Did you try to use a server with that value. And then use clients in your patches/abstractions to query this value to the server at startup ? I could be a possibility... ++
Jack
Le 06/01/2017 à 16:05, Jérôme Abel a écrit :
a [text] (and get its first line from your abs)
Inside the main patch, I use [text] to read constant values from a textfile. Then I could store them in containers like [symbol], [float], [list] in each abstractions but it seems (for me) not flexible. It does not allow to open a patch or an abstraction which needs thoses values. I can reload the textfile when the patch is opened but I don't like this design : when I reload the textfile I trigger values into the 2 patches.
My way now is a [text] loader of the same textfile into my main patches, called once at the startup.
The [pv] object from cyclone is a good choice, thanks for the tip. It just needs to be created in a parent level.
But if you only have to get its constant value (and not to modify it) then you could just call a shared abstraction in your abs, that would just send the symbol to an outlet?
Do you mean one [text] loader into each abstractions ?
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
In fact, i was thinking about this system :
- one server patch (or you can use an other programming language)
managing the text to share and waiting a connection from a client to share this text
- patches and/or abstractions client that need this text. They just have
to connect to the server at startup.
With this solution, you can use different patches/abstractions, on different intances of Pd (on different computer if needed) to share the same text. ++
Jack
Le 10/01/2017 à 15:45, Antoine Rousseau a écrit :
Do you mean one [text] loader into each abstractions ?I just meant loadbanging a symbol (or a message). e.g:
shared_symbol.pd:
[loadbang] | [symbol MySharedSymbol] | [outlet]
Then patches calling [shared_symbol] will get the symbol at load time.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-01-06 18:30 GMT+01:00 Jack <jack@rybn.org mailto:jack@rybn.org>:
Hello Jérôme, Did you try to use a server with that value. And then use clients in your patches/abstractions to query this value to the server at startup ? I could be a possibility... ++ Jack Le 06/01/2017 à 16:05, Jérôme Abel a écrit : >> a [text] (and get its first line from your abs) > > Inside the main patch, I use [text] to read constant values from a > textfile. Then I could store them in containers like [symbol], [float], > [list] in each abstractions but it seems (for me) not flexible. It does > not allow to open a patch or an abstraction which needs thoses values. I > can reload the textfile when the patch is opened but I don't like this > design : when I reload the textfile I trigger values into the 2 patches. > > My way now is a [text] loader of the same textfile into my main patches, > called once at the startup. > > The [pv] object from cyclone is a good choice, thanks for the tip. It > just needs to be created in a parent level. > >> But if you only have to get its constant value (and not to modify it) >> then >> you could just call a shared abstraction in your abs, that would just >> send >> the symbol to an outlet? > > Do you mean one [text] loader into each abstractions ? > _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list <https://lists.puredata.info/listinfo/pd-list>
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Antoine Rousseau -
Jack -
Jérôme Abel