<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'>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: l2ork-dev@disis.music.vt.edu<br>From: ico@vt.edu<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 class=ecxmoz-cite-prefix>On 5/23/2016 8:56 AM, Liam Goodacre
wrote:<br>
</div>
<blockquote cite="mid:DUB131-W26B8ABDA9C18E46E9B5718FC4E0@phx.gbl">
<div dir=ltr>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<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 class=ecxmimeAttachmentHeader></fieldset>
<br>
<pre>_______________________________________________
L2Ork-dev mailing list
<a class=ecxmoz-txt-link-abbreviated href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a>
<a class=ecxmoz-txt-link-freetext 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
L2Ork-dev@disis.music.vt.edu
http://disis.music.vt.edu/listinfo/l2ork-dev </div></body>
</html>