Videonisse Posted December 12, 2014 Report Posted December 12, 2014 Just a thought, if the current HW makes it difficult to implement and it breaks principals for programming, isn't it also then very difficult to get this reliable without huge investment in time? If yes,wouldn't a gen2 HW be a much better base? Why not postpone support for this feature in current HW and instead focusing on cleaning up bugs in current SW (for example the Native Harmony profile) and try to get out a new hardware version of Flirc. As I have understood, your code base is now prepared to do so, correct? :) Quote
jason Posted December 12, 2014 Report Posted December 12, 2014 Just a thought, if the current HW makes it difficult to implement and it breaks principals for programming, isn't it also then very difficult to get this reliable without huge investment in time? If yes,wouldn't a gen2 HW be a much better base? Why not postpone support for this feature in current HW and instead focusing on cleaning up bugs in current SW (for example the Native Harmony profile) and try to get out a new hardware version of Flirc. As I have understood, your code base is now prepared to do so, correct? :) You're very smart. I'm going to do everything I can so that bringing this feature, it will work on any version of hardware/chip. Quote
calavera Posted January 24, 2015 Author Report Posted January 24, 2015 It's a long time since I started this thread, but I want to let you know that this feature would still be very appreciated although I had to buy another remote. I'm looking forward to switching back to apple remote as soon as it is implemented. Quote
FelixFlutsch Posted February 25, 2015 Report Posted February 25, 2015 ++support, please. or maybe there is a workaround to have this long-press bound to another key on the (silver) apple-remote, without losing a single button on the remote? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.