cosmicvoid,
I hate those "Please Wait" screens. I developed a command queue. This queue is passed from activity to activity. A command is pushed onto this queue with an execution delay. One can be assured that this command will be held, then executed -- no matter which screen is current. This makes the remote seem so much more responsive because you don't ever seem to be waiting. If I need to hold TV commands for ten seconds or so after POWER ON, I can immediately go to the cable page and set my channel while the pokey TV is waking up. When the TV is ready, its Input command is executed. "Please Wait" makes the remote seem slow. In my scheme, staring at a dark TV screen places the blame where it belongs.
Another plus to this scheme is that the operator cannot overrun the remote or controlled device. This is wonderful when dealing with slow cable boxes. One can quickly queue up a bunch of commands that might require the best part of a minute (or more) to execute. I am constantly overrunning cable boxes when using their native remote. Now, I can enter a channel number at light speed and move on while the commands are delivered to the box at a pace that it can digest. (And this "pace" might change with cable box firmware updates.)
Also, it is irksome if the system starts up and the previous Volume setting is too high for current conditions. With a "Please Wait", one is trapped at this excessive Volume until the "Please Wait" finishes because the Pronto buttons are locked out. With my Queue, the Volume buttons are always available.
Last edited by buzz on September 21, 2016 08:01.