Issue 58: More flexible command definition
Project Member Reported by octavian...@gmail.com, Apr 18, 2013
"ProTONE commands can be very cryptic to end users. They don't need to know that \r\n""Playback?CmdLoad"" should be used to open load files dialog. They just need to know that there is a command for which ProTONE will open the load dialog, and so on.\r\n\r\nTherefore it is proposed to define template files containing standard ProTONE commands. For such files the ""Data to output pin"" field becomes ""Command name"" and it will display a friendly command name that cannot be altered by the user. The user will still have to learn button codes by using Detect.\r\n\r\nThere has to be a template file per each type of input pin.\r\nThe program will be enhanced with extra buttons from where the user will have the possiblity to:\r\n\r\n- add a template to the already existing working configuration.\r\n- backup/export the working configuration\r\n- import an existing backed up configuration, with options to merge with the working configuration or to replace it.\r\n\r\n"
Apr 18, 2013
Project Member #1 octavian...@gmail.com
(No comment was entered for this change.)
Owner: octavian...@gmail.com
Apr 18, 2013
Project Member #2 octavian...@gmail.com
(No comment was entered for this change.)
Labels: ReportSource-DevQA
Apr 29, 2013
Project Member #3 octavian...@gmail.com
(No comment was entered for this change.)
Owner: ---
Nov 29, 2013
Project Member #4 octavian...@gmail.com
(No comment was entered for this change.)
Status: RegressionTest
Dec 2, 2013
Project Member #5 octavian...@gmail.com
(No comment was entered for this change.)
Status: Closed
Sep 8, 2014
Project Member #6 octavian...@gmail.com
(No comment was entered for this change.)
Status: RegressionTest
Sep 8, 2014
Project Member #7 octavian...@gmail.com
(No comment was entered for this change.)
Status: Closed