<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 35: Automatic Custom Protocol Tracking</title><link>https://sourceforge.net/p/controlremote/feature-requests/35/</link><description>Recent changes to 35: Automatic Custom Protocol Tracking</description><atom:link href="https://sourceforge.net/p/controlremote/feature-requests/35/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 03 Sep 2010 19:19:25 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/controlremote/feature-requests/35/feed.rss" rel="self" type="application/rss+xml"/><item><title>Automatic Custom Protocol Tracking</title><link>https://sourceforge.net/p/controlremote/feature-requests/35/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;As Rob describes in this post:  (http://www.hifi-remote.com/forums/viewtopic.php?p=90746#90746)  I would like RMIR to look at the two executors and if they're the same, just save one copy. If the new $01FF executor is different to the existing $01FF executor, RMIR should scan all the other executors to see if the code is the same as another executor (as the user could have added it already under a different PID). If no match is found, RMIR could either find the next free PID below $01FF and select it automatically, or it could give the user the opportunity to select a new PID. Maybe this could be configurable via an "expert" option.&lt;/p&gt;
&lt;p&gt;Once a new PID is selected, the user should be asked to save the RMDU file so that the right PID is used next time the upgrade is modified.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Capn Trips</dc:creator><pubDate>Fri, 03 Sep 2010 19:19:25 -0000</pubDate><guid>https://sourceforge.net0834e3fda922f906808749c49139b33925ea0584</guid></item></channel></rss>