OK,

I got the "send me your codes" email from Brett too.

Not that I mind sharing my work, but at this point, and i'm asking for everyones help here, I think

it is way more important to get some, or all of the changes we have all been asking for for the last 12 months into the new software, since RTI doesn't seem to like to periodic updates like everyone else does, unless they are releasing product.

This outweights any IR database management, which we as a CI entity, can maintain ourselves. Look at the evolution of the megalist (not without problems, but we can do it ourselves as a group)

I would much rather see RTI spend their software development budget on this, over the IR database.

So I propose digging up all that "here's what we woudl like to see" stuff, and email it directly to them. Bombard them with it so they get the message.

I already sent a list to Brett. Let's get it going.

Just my opinion

another thing to remember is there are other countries that use RTI as well and they have their databases too that RTI keeps tabs on, so they have the US, Germany, Europe, japan?

so its more than just our little list of codes.

I think letting them know what we would like to see is great, just remember that they will have to keep the continuity through out the rest of the world as well, and take in the rest of the worlds ideas too.

the 232 database would be nice, IR testing from learner or remotes,

True Variables and Dynamic buttons states are my biggest.

I agree. Give them something achievable rather than bombardment. Let's just decide amongst each other what are the three most critical ideas (regardless of our own personal bias) and send them the three. I would rather see something than nothing. It's been awhile since anything powerful has been implemented. I doubt anyone really asked for the scrolling list feature.

I am game.

We should try and layout a few guidelines so that we can keep the ideas clear and documentable. I have seen these threads go nowhere because there is no focus and no limits.

May I suggest that the thread continue for a fixed period of time, say 1-4 weeks.

Also...
...perhaps listing no more that three ideas per post in a clear numbered list?
...post nothing but the list when submitting suggestions?
...discussion and debate is welcome, however, no lengthy explanations or justifications unless a dialog starts on a particular idea that needs clarification.

Let me know if I should kiss off with ideas.

If not, I will throw out a post...

1) The ability to create an executable file so the TTD file can be sent electronically and installed without access to TTD.

2) The ability to batch edit port routing options by device profile, grouped touchscreen and hard buttons and for multiple pages.

3) The ability to batch edit IR routing options for channel macros after they have been created without using the wizard to rebuild the channel macros.

I agree that about the least important is updated code lists.

1. I also really like the variables and dynamic buttons. (FD, where is the thread that you gave that detailed example?)

2. I strongly second IR testing!!! not just for new codes learned but because older files may match new equipment.

3. I would like to see the library browser as a menu tree that would allow me to see the codes from several different devices at the same time, similer to SpeakerCraft in their EZ-tools software. And do the same thing to the macro editor.

1. Self packaged executable files for customers / co-workers.

2. IR Testing capability w/ true macro emulation, including processors!

3. Grouping of pages or Containers for pages.

-jc

Also, I read something on IP recently about problems with macros not being able to insert page flips for "please wait" animations because of the processor executing the macro but the page flips are stored on the remote. A deffinate pain in the ass.

I agree, there is a clear reason for loss of ability when using the remote vs processor, but I believe that they can improve on this. Joey also brings up a money saving point by allowing executable files for customers to load up themselves..

Let's play this out. Everyone submit 4 suggestions. We will vote them down, come up with a top 5 by taking votes. We will then submit to RTI formally, not just with email, but with a clear letterhead. Here are mine:

1) Ability to test codes with remote (macros included)

2) Dynamic buttons as PART of the true variable addition

3) Comment field in the IR library to decipher bad codes or notable problems.

4) Allow more flexibilty when setting the remote to trigger vs standalone

1) A flag status window to see the status of any/all flags you have set when testing in emulation mode. Also, allow you to run emulation in a step by step mode so that you can better track down where in the programming a problem lies.

Can you clarify #4 with more specifics?

I agree,

along with just plain fixing!!! Expanding basic port addressing functionality is a must, For instance, we should not have to put a button into stand alone mode before we can address multiple RP-6 modules, or to combine IR with RF functionality in a macro, this should be a redundant, automatic feature

RTI also seriously needs to address batch edit features in TTD

And my biggest pet peeve is that you should be able to edit or add anything while in the channel macro wizard, including port address specific things on the fly.