Sorry I’m late to the party on this. I took a look at the Roku documentation on the active app query–it looks like it would be pretty straightforward to add support for it to my plugin. I’ll try to take a stab at that tonight.
One thing I would propose is that since the original Roku app used the Media Input Source capability to define the available apps (in
device.SupportedInputSources), we should probably use the
device.InputSource to store the active one (rather than the
device.ActiveApp attribute). That would seem to make the most sense, right? I believe that is how the plugin changes the active app also, although I personally have not used that functionality, so I think that would be the most consistent approach within Home Remote.
This is more a question for @bill: per the Roku documentation, there are some additional available “active apps” that do not seem to be valid as “launchable”: homescreen/Roku, screensaver, and black. Any thoughts on whether it is a problem to set
device.InputSource to a value not in
Lastly, I wanted to quickly clarify that my Roku plugin does NOT require the MCE stuff–it merely supports the same commands as that plugin so that you can use a common keyboard interface with both devices.