hello hackers,
shall we introduce a mechanism that guarantees unique object names across the published pd libraries? the problem: for example, both zexy and gem have an external called "abs~". i guess you cannot tell which one gets loaded after you had loaded both libraries.
at the pure database, http://iem.kug.ac.at/pdb/ i made a list of all existing externals and pd objects - you can look there when making an external if its name is free. (and, while you are there, please check the entries of your objects - there is a good chance that some are outdated or even missing)
would it be good to have a kind of registration mechanism? eg. a possibility to registrate names (or fractions of names) on the database?
norbert
I read:
for example, both zexy and gem have an external called "abs~". i guess you cannot tell which one gets loaded after you had loaded both libraries.
same with streamin/out~ in ggee/zexy
regards
x
don`t forget hslider in ggee & iemlib
regards dieb
I read:
for example, both zexy and gem have an external called "abs~". i guess you cannot tell which one gets loaded after you had loaded both libraries.
same with streamin/out~ in ggee/zexy
regards
x
gro.tgnilk@31beid
'>< esrever ralacs tnirp' e- lrep | \ ".egaugnal yna ni edoc ylbmessa etirw nac sremmargorp laer" ohce
This is going to be a never-ending problem...! suppose someone uses lib 1 and lib 2, and has a patch using "wack" from lib 2, and then the lib 1 author introduces a "wack" object. The only way I can think of to protect against this problem is to somehow declare to Pd that, in the context of a given patch, "wack" should be taken from lib 2. Hmm, then someone merges lib2 and lib 3, so the declaration then has to change... I have no idea how to deal with this in general..
cheers MIller
On Thu, Jul 19, 2001 at 05:51:50PM +0200, Norbert Math wrote:
hello hackers,
shall we introduce a mechanism that guarantees unique object names across the published pd libraries? the problem: for example, both zexy and gem have an external called "abs~". i guess you cannot tell which one gets loaded after you had loaded both libraries.
at the pure database, http://iem.kug.ac.at/pdb/ i made a list of all existing externals and pd objects - you can look there when making an external if its name is free. (and, while you are there, please check the entries of your objects - there is a good chance that some are outdated or even missing)
would it be good to have a kind of registration mechanism? eg. a possibility to registrate names (or fractions of names) on the database?
norbert
for those of you that haven't seen it already, this excellent latency report was retreived from the LAD list. guess which came first - though only by half a millisecond ; ) OsX came out v'well and also Win2000.
http://mambo.peabody.jhu.edu/~karlmac/publications/latency-icmc2001.pdf
de|
_ / a -> b, b ->c, a -> d, d -> c ...and so on... \ _
hi list, is it possible to set the size of the ticks in arrays? i would like to have continuous lines from the top boundary of an array to the bottom. and some other arrays-questions: is it possible to change the color of a graph? is it possible to prevent a graph from going outside the boundarys when drawing with the mouse? and is it possible to label certain points with numbers or names (like "ten" or "123" on point 10)? bitte, danke. marius.
Miller Puckette hat gesagt: // Miller Puckette wrote:
This is going to be a never-ending problem...! suppose someone uses lib 1 and lib 2, and has a patch using "wack" from lib 2, and then the lib 1 author introduces a "wack" object. The only way I can think of to protect against this problem is to somehow declare to Pd that, in the context of a given patch, "wack" should be taken from lib 2. Hmm, then someone merges lib2 and lib 3, so the declaration then has to change... I have no idea how to deal with this in general..
Maybe one could introduce some kind of namespace like in C++. This could be an object like [namespace gem], that changes the namespace of the surrounding patch.