-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On a side note, something like this, or improvements along these lines, I think would greatly improve the ability to do dynamic patching. Right now it's difficult to do connects with messages because I have no idea what number each object is. (Or maybe there's a more straightforward solution to this particular issue?)
Best, Ian
Thomas Grill wrote: | Hi, | something like GUIDs would be great, but i think they should be somehow | readable (not Microsoft-like). | What about a running index per patcher, that is incremented every time an | object is created? | Or a date/time/microtime combination? | For me the integration into the PD file format is not important since | there's no real place for other metadata either. | A discussion about a general XML format is really appreciated. | | best greetings, | Thomas | | ----- Original Message ----- | From: "Mathieu Bouchard" matju@sympatico.ca | To: "Martin Peach" martinrp@vax2.concordia.ca | Cc: "Georg Holzmann" grhPD@gmx.at; pd-dev@iem.at | Sent: Friday, December 10, 2004 10:48 AM | Subject: Re: [PD-dev] PD patches in XML | | | |>On Thu, 9 Dec 2004, Martin Peach wrote: |> |>>Mathieu Bouchard wrote: |>> |>>>problem is that object ID's change too often, because if an object is |>>>deleted, its ID is not skipped, and a bunch of objects are renumbered | | just | |>>>so that the ID is not skipped, because there is no way in the format | | to | |>>>skip one. I think this has to be solved in the pd internals first, in | | the | |>>>runtime storage of a patch, because it's where the renumbering (or the |>>>ignoring of numbering) normally happens. |>> |>>This might be a good time to introduce the Globally Unique Identifer, |>>perhaps in the form of a 32-bit random number that is generated for each |>>object in a patch and never reused -- the running pd program would |>>maintain a list of all GUIDs in use in the current session. |> |>Well, I was thinking of something along the lines of a locally unique |>identifier, whose scope is exactly one patcher, because the problem with |>changing indices happens exactly at the patcher level. I don't know what |>GUID's would bring at this point. I can't think of any nice way of |>introducing GUID's easily in the .pd format except by making each object |>two lines of code instead of one. What do you have in mind? |> |>_____________________________________________________________________ |>Mathieu Bouchard -=- Montréal QC Canada -=- http://artengine.ca/matju |> |> |> |>_______________________________________________ |>PD-dev mailing list |>PD-dev@iem.at |>http://iem.at/cgi-bin/mailman/listinfo/pd-dev |> |> | | | | _______________________________________________ | PD-dev mailing list | PD-dev@iem.at | http://iem.at/cgi-bin/mailman/listinfo/pd-dev