infinitytec Posted February 18, 2023 Report Share Posted February 18, 2023 It would be nice to be able to export a PDF or something that details the remote's button layout. I feel that certain levels of configuration would be a must, as certain buttons might not need much or any explanation. For example, if the number buttons are mapped to numbers, maybe only a label is needed rather than a separate description for each button. I think this would help if my layout gets too complex. Quote Link to comment Share on other sites More sharing options...
Nathan Posted February 20, 2023 Report Share Posted February 20, 2023 On 2/18/2023 at 11:44 AM, infinitytec said: It would be nice to be able to export a PDF or something that details the remote's button layout. I feel that certain levels of configuration would be a must, as certain buttons might not need much or any explanation. For example, if the number buttons are mapped to numbers, maybe only a label is needed rather than a separate description for each button. I think this would help if my layout gets too complex. Hi, I'm not sure if I follow what you're asking for. Do you mean like being able to print out a list of the buttons connected to the Flirc remote? Quote Link to comment Share on other sites More sharing options...
infinitytec Posted March 5, 2023 Author Report Share Posted March 5, 2023 On 2/20/2023 at 1:38 PM, Nathan said: Hi, I'm not sure if I follow what you're asking for. Do you mean like being able to print out a list of the buttons connected to the Flirc remote? Yep! Quote Link to comment Share on other sites More sharing options...
dsample Posted March 9, 2023 Report Share Posted March 9, 2023 It would certainly be nice to have an ink-friendly version to print as a reference, especially when you have guests and particularly complex setups Quote Link to comment Share on other sites More sharing options...
Nathan Posted March 9, 2023 Report Share Posted March 9, 2023 I think this could be doable. Right now we already have a way to export your settings into a .skip file that shows the commands after "label":. Stripping out everything except those commands, the model, and the brand, and putting a little formatting in should be pretty doable. We can put it on the list, but we definitely have some other priorities that are currently higher. I'm actually wondering if this might be something the community would be interested in doing. A script (maybe even an open source script!) to read and print out a human readable skip file could be right up the alley of one of our more tech savvy users. Quote Link to comment Share on other sites More sharing options...
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.