<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Yes, that's what I was thinking--the first object is 0, the second is 1, etc. They would also have to update in real time, ie. if I delete the first object, then the old object 1 is now object 0, the old object 2 is now 1, etc. [iemguts/canvasselect] can already identify and print these numbers, but of course they're not visible in the patch.<br><br>I was thinking the same for the connection wires (ie. ordinal numbers, as you said) although the more I think about it the less sense this makes, as connections aren't numbered per se. The only instance where it would be useful to know these numbers would be to disambiguate an object with multiple connections coming out of the same outlet, but this is a practice that is discouraged anyway.<br><br>What do you think?<br><br><div><hr id="stopSpelling">Date: Mon, 23 May 2016 15:28:05 -0400<br>From: ico@vt.edu<br>To: l2ork-dev@disis.music.vt.edu<br>Subject: Re: [L2Ork-dev] feature request, view object number<br><br><p dir="ltr">So, if I understand you correctly the first object ever created on the canvas would have ordinal number of 0 and the second object would have number one and so on and so forth. I assume the same would be true for all connection wires or would they be more specific to each object they are connected to?</p>
<p dir="ltr">-- <br>
Ivica Ico Bukvic, D.M.A.<br>
Associate Professor<br>
Computer Music<br>
ICAT Senior Fellow<br>
Director -- DISIS, L2Ork<br>
Virginia Tech<br>
School of Performing Arts – 0141<br>
Blacksburg, VA 24061<br>
(540) 231-6139<br>
<a href="mailto:ico@vt.edu">ico@vt.edu</a><br>
<a href="http://www.performingarts.vt.edu" target="_blank">www.performingarts.vt.edu</a><br>
<a href="http://disis.icat.vt.edu" target="_blank">disis.icat.vt.edu</a><br>
<a href="http://l2ork.icat.vt.edu" target="_blank">l2ork.icat.vt.edu</a><br>
<a href="http://ico.bukvic.net" target="_blank">ico.bukvic.net</a></p>
<div class="ecxgmail_quote">On May 23, 2016 14:20, "Liam Goodacre" <<a href="mailto:liamg_uw@hotmail.com">liamg_uw@hotmail.com</a>> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">I don't know what the glist stack is. I'm talking about the object creation order that corresponds to the object's placement in the pd file. For example, in the command "connect x 0 y 1", x and y are the object numbers.<br><br><hr>To: <a href="mailto:l2ork-dev@disis.music.vt.edu" target="_blank">l2ork-dev@disis.music.vt.edu</a><br>From: <a href="mailto:ico@vt.edu" target="_blank">ico@vt.edu</a><br>Date: Mon, 23 May 2016 13:03:05 -0400<br>Subject: Re: [L2Ork-dev] feature request, view object number<br><br>
Thank you for the suggestion. Are you talking about the memory
location on the glist stack? (e.g. like the one that canvas name
has)<br>
<br>
<br>
<div>On 5/23/2016 8:56 AM, Liam Goodacre
wrote:<br>
</div>
<blockquote>
<div dir="ltr">
<div dir="ltr">What do you think about this for a new L2Ork
feature? A new option in the edit menu that places little
numbers next to each object on the canvas, according to their
creation order. This would be really useful for dynamic
patching, ie. if you're trying to connect or delete objects
and you need to know their number. It would also fit nicely
with the "send to front/back" feature that you've already
made.<br>
<br>
A couple of other thoughts:<br>
<br>
1. It would probably be best if this could only come into
effect when edit mode is on, a bit like the little re-size
dots in the corner of a "bang". It's probably also best if
it's an additional option rather than contiguous with edit
mode, as the numbers might get confusing or annoying in larger
patches.<br>
<br>
2. A further possibility would be to have the same option for
connection numbers. This would be immediately useful, as
connection order is integral to PD functioning. On the other
hand it might also provide less incentive to use trigger, and
hence lead to sloppy patching.<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
L2Ork-dev mailing list
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a>
<a href="http://disis.music.vt.edu/listinfo/l2ork-dev" target="_blank">http://disis.music.vt.edu/listinfo/l2ork-dev</a></pre>
</blockquote>
<br>
<br>_______________________________________________
L2Ork-dev mailing list
<a href="mailto:L2Ork-dev@disis.music.vt.edu" target="_blank">L2Ork-dev@disis.music.vt.edu</a>
<a href="http://disis.music.vt.edu/listinfo/l2ork-dev" target="_blank">http://disis.music.vt.edu/listinfo/l2ork-dev</a> </div></div>
<br>_______________________________________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="http://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">http://disis.music.vt.edu/listinfo/l2ork-dev</a><br></blockquote></div>
<br>_______________________________________________
L2Ork-dev mailing list
L2Ork-dev@disis.music.vt.edu
http://disis.music.vt.edu/listinfo/l2ork-dev</div> </div></body>
</html>