"Hexamon" wrote:
Hate to be a pain with this but given all these issues, wouldn't it be a good idea to:
Don't worry, I'm sure I'm a pain all the time.
🙂
1. Provide better diagnostics for the developer community (or better documentation on understanding how to use the exiting ones) in identifying the issues related to the player?
There's supposed to be some enhancements coming to the debugger soon (maybe some are in 2.8? I should look). See
viewtopic.php?f=34&t=32853I think the best thing we can do as developers is get into the beta program and make sure to test extensively there. This may mean getting a second unit so one can be in the beta and one not for better test coverage, but at $60 for a base model it shouldn't be too hard to get that second model.
2. Provide a way to either temporarily disable automatic updates of the firmware or a mechanism to fall back to a known-to-be-good version of it?
This has been discussed extensively. I think if you really think about the ramifications of allowing people to hold their player back from newer firmware releases, you'll come to the same conclusion I did (and Roku has, obviously). I think a group of users running an ever expanding set of different firmware releases complaining about features not working, bug that were long ago fixed, and inconsistent look and feel would greatly outweigh any benefit gained, especially when more active participation in the beta will probably keep most of the problems from this release cycle from happening again.
P.S. You can
say temporarily, but I think in practice if it's available to users they will find a way to make it permanent.
-- GandK Labs
Check out Reversi! in the channel store!