Reply to thread

Message

<blockquote data-quote="barnabas1969" data-source="post: 774158" data-attributes="member: 114414">mm (and the others above),Thanks for your response, and I apologize for my rudeness... I edited my post.I'm trying to change the program to allow a macro to be run from the Windows command prompt with an optional timeout value.&nbsp; I'm not experienced with C#, so I was finding my way around and reading documentation that I could find on the web.The SendWindowsMessage (not to be confused with the Windows function SendWindowMessage) calls SendMessageTimeout with a hard-coded timeout value of 1000 milliseconds.&nbsp; I was attempting to change the SendWindowsMessage function so that it can accept a 5th parameter that defaults to 1000 milliseconds.&nbsp; Then, in the SendCopyDataMessage function, I wanted to split the variable &quot;data&quot; into two separate values... the first one would be the name of the macro to run, and the second would be the timeout... delimited by a pipe character since pipes are not allowed in a Windows filename and thus not allowed in the name of a macro.I gave up on it since I had received no response here... and because my workaround works.&nbsp; However, it would still be nice to get this working properly.&nbsp; When a macro contains a pause, you can't run that macro from a command prompt due to the hard-coded timeout.&nbsp; It would be wonderful if this could be fixed, because I can see many uses for macros with pauses that need to be called from the command prompt.I've also found another bug that has to do with loading and saving variables in a macro.&nbsp; Whenever I try to save a variable, my VariablesList file gets created with bad data.&nbsp; I found another post (<a href="http://https://forum.team-mediaportal.com/ir-server-suite-irss-165/patch-translator-doesnt-load-variables-macro-correctly-75119/#post544162" target="_blank">here</a>) that mentions this very bug which was supposedly fixed.I'm happy to test and provide feedback.&nbsp; I would like to learn C# and fix some of this stuff myself, but time is limited.&nbsp; If I can get this all working correctly, I will be happy to donate to the project.&nbsp; I understand that it takes money to run a project like this and that very few people actually donate.Thank you,Brian</blockquote>

[QUOTE="barnabas1969, post: 774158, member: 114414"] mm (and the others above), Thanks for your response, and I apologize for my rudeness... I edited my post. I'm trying to change the program to allow a macro to be run from the Windows command prompt with an optional timeout value. I'm not experienced with C#, so I was finding my way around and reading documentation that I could find on the web. The SendWindow[B]s[/B]Message (not to be confused with the Windows function SendWindowMessage) calls SendMessageTimeout with a hard-coded timeout value of 1000 milliseconds. I was attempting to change the SendWindowsMessage function so that it can accept a 5th parameter that defaults to 1000 milliseconds. Then, in the SendCopyDataMessage function, I wanted to split the variable "data" into two separate values... the first one would be the name of the macro to run, and the second would be the timeout... delimited by a pipe character since pipes are not allowed in a Windows filename and thus not allowed in the name of a macro. I gave up on it since I had received no response here... and because my workaround works. However, it would still be nice to get this working properly. When a macro contains a pause, you can't run that macro from a command prompt due to the hard-coded timeout. It would be wonderful if this could be fixed, because I can see many uses for macros with pauses that need to be called from the command prompt. I've also found another bug that has to do with loading and saving variables in a macro. Whenever I try to save a variable, my VariablesList file gets created with bad data. I found another post ([URL="http://https://forum.team-mediaportal.com/ir-server-suite-irss-165/patch-translator-doesnt-load-variables-macro-correctly-75119/#post544162"]here[/URL]) that mentions this very bug which was supposedly fixed. I'm happy to test and provide feedback. I would like to learn C# and fix some of this stuff myself, but time is limited. If I can get this all working correctly, I will be happy to donate to the project. I understand that it takes money to run a project like this and that very few people actually donate. Thank you, Brian [/QUOTE]

Verification