<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Trace back control IDs to their actor inputs, or vice versa-anyway to do this?]]></title><description><![CDATA[<p>Hi All,</p><p><br />I have a monster patch that I am trying to clean up. One problem is that I find it hard to to trace the control IDs to their actor inputs.</p><p>Is there anyway to do this in 3.2.6?</p><p><br />Thanks for your help,</p><p><br />Eric</p>]]></description><link>https://community.troikatronix.com/topic/8978/trace-back-control-ids-to-their-actor-inputs-or-vice-versa-anyway-to-do-this</link><generator>RSS for Node</generator><lastBuildDate>Tue, 10 Nov 2026 21:28:27 GMT</lastBuildDate><atom:link href="https://community.troikatronix.com/topic/8978.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 10 Sep 2024 13:25:09 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Trace back control IDs to their actor inputs, or vice versa-anyway to do this? on Sun, 15 Sep 2024 01:05:43 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/1435">@woland</a> Maybe, if this feature is implemented one day (I also tend to do monster patches...) maybe one of its output is to generate a multi column list where in each line there is one entry (control number on column a, control name on column b, connected actor name on column c connected input on column d and active link status on column e). I think that the status is important because actors in the patching widows don't lose the control ID link number attached to their inputs if the control is deleted. Also it would be nice to have a visual feedback on that (control id number background in control window and actors in patching windows that are not connected could be red if not connected and green if actively assigned). Just a thought</p>]]></description><link>https://community.troikatronix.com/post/54924</link><guid isPermaLink="true">https://community.troikatronix.com/post/54924</guid><dc:creator><![CDATA[Armando]]></dc:creator><pubDate>Sun, 15 Sep 2024 01:05:43 GMT</pubDate></item><item><title><![CDATA[Reply to Trace back control IDs to their actor inputs, or vice versa-anyway to do this? on Fri, 13 Sep 2024 17:17:44 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/233">@ursullivision</a></p><p>I have added this to our list of Feature requests.</p>]]></description><link>https://community.troikatronix.com/post/54920</link><guid isPermaLink="true">https://community.troikatronix.com/post/54920</guid><dc:creator><![CDATA[DusX]]></dc:creator><pubDate>Fri, 13 Sep 2024 17:17:44 GMT</pubDate></item><item><title><![CDATA[Reply to Trace back control IDs to their actor inputs, or vice versa-anyway to do this? on Thu, 12 Sep 2024 09:45:48 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/233">@ursullivision</a> said:</p>
<blockquote>I have a monster patch that I am trying to clean up. One problem is that I find it hard to to trace the control IDs to their actor inputs.</blockquote>
<p> No, I usually keep track of this in a Comment actor when I build larger patches.</p>]]></description><link>https://community.troikatronix.com/post/54918</link><guid isPermaLink="true">https://community.troikatronix.com/post/54918</guid><dc:creator><![CDATA[Woland]]></dc:creator><pubDate>Thu, 12 Sep 2024 09:45:48 GMT</pubDate></item></channel></rss>