Reply to thread

Message

<blockquote data-quote="huha" data-source="post: 258286" data-attributes="member: 63847">Aaron, after your response I first thaught I would not need the commandline option anymore.But working a few more weeks with your great tool, I still would like to ask you for implementing the command line option. It would allow me to define one buttom on the remote as a shift button and nearly double the available keys.I would then assign the Shift button with the run command&nbsp;Translator.exe -Config &quot;C:\Config Files\Config_Shift.xml&quot;I could use this xml file to assign a full layer of additional commands and switch back to the main layer by using the same button with the run commandTranslator.exe -Config &quot;C:\Config Files\Config.xml&quot;where Config.xml describes the original main layer functions.Another variation of this idea would be to assign a small script to a &quot;Shift&quot; Button like Translator.exe -Config &quot;C:\Config Files\Config_Shift.xml&quot;Sleep(2000)Translator.exe -Config &quot;C:\Config Files\Config.xml&quot;This script would activate for 2s the shift layer and then switch back to the original layer. It would allowto define special functions by using the shift key and another key on the remote.Independent of that i do have a second question. Is it possible to transfer the current active application and thexml file as a parameter when assigning a program start from the translator?I am writing right now an autoit script for displaying the key assignment when pushing a help button on the remote. This script is evaluating the translator xml file and displaying the actual key assignment of the remote for the active application.Right now I am calling this script by defining a key and use the application name and the xml file name as an argument to the autoit script.For that i need to define the remote help button for each application separately. If there would be a variable in the translator e.g. STR_APPLICATIONand STR_XMLFILE it would be possible to assign this button only once in the system wide settings.</blockquote>

[QUOTE="huha, post: 258286, member: 63847"] Aaron, after your response I first thaught I would not need the commandline option anymore. But working a few more weeks with your great tool, I still would like to ask you for implementing the command line option. It would allow me to define one buttom on the remote as a shift button and nearly double the available keys. I would then assign the Shift button with the run command Translator.exe -Config "C:\Config Files\Config_Shift.xml" I could use this xml file to assign a full layer of additional commands and switch back to the main layer by using the same button with the run command Translator.exe -Config "C:\Config Files\Config.xml" where Config.xml describes the original main layer functions. Another variation of this idea would be to assign a small script to a "Shift" Button like Translator.exe -Config "C:\Config Files\Config_Shift.xml" Sleep(2000) Translator.exe -Config "C:\Config Files\Config.xml" This script would activate for 2s the shift layer and then switch back to the original layer. It would allow to define special functions by using the shift key and another key on the remote. Independent of that i do have a second question. Is it possible to transfer the current active application and the xml file as a parameter when assigning a program start from the translator? I am writing right now an autoit script for displaying the key assignment when pushing a help button on the remote. This script is evaluating the translator xml file and displaying the actual key assignment of the remote for the active application. Right now I am calling this script by defining a key and use the application name and the xml file name as an argument to the autoit script. For that i need to define the remote help button for each application separately. If there would be a variable in the translator e.g. STR_APPLICATION and STR_XMLFILE it would be possible to assign this button only once in the system wide settings. [/QUOTE]

Verification