09-09-2015, 05:39 AM
The "wait(0 WC win(...))" could work but implies that I have to set the following in the code itself:
- actual keyword to look for: "test"
- and the application to start: "mspaint"
Because I want to give the user the option to add/modify multiple keywords and applications the compiled exe will use an external textfile. In the "For i 0..." loop the arr[i] would be matched with each line of the textfile.
The textfile in which the user defines the string to look for in window title and what to start.
The textfile could look like this:
[keyword_app_list]
test_1|c:\test\app_1.exe
test_2|c:\test\app_2.exe
The pipe symbol splits/delimits the 2 values first value keyword, second value application to start.
I do not know if compiled exe code constantly reads code from the HD and then executes OR once the exe is loaded in memory it does not access the .exe on the HD (making it hard drive friendly at least).
But then I need to know if continually repeating the code does not impact the machines performance (processor and or RAM-memory wise).
I can understand it is difficult to give an estimation on this or that it is very difficult to create processor/ram friendly code based on constant execution of code. It is not extremely important, but I was very curious about this.
- actual keyword to look for: "test"
- and the application to start: "mspaint"
Because I want to give the user the option to add/modify multiple keywords and applications the compiled exe will use an external textfile. In the "For i 0..." loop the arr[i] would be matched with each line of the textfile.
The textfile in which the user defines the string to look for in window title and what to start.
The textfile could look like this:
[keyword_app_list]
test_1|c:\test\app_1.exe
test_2|c:\test\app_2.exe
The pipe symbol splits/delimits the 2 values first value keyword, second value application to start.
I do not know if compiled exe code constantly reads code from the HD and then executes OR once the exe is loaded in memory it does not access the .exe on the HD (making it hard drive friendly at least).
But then I need to know if continually repeating the code does not impact the machines performance (processor and or RAM-memory wise).
I can understand it is difficult to give an estimation on this or that it is very difficult to create processor/ram friendly code based on constant execution of code. It is not extremely important, but I was very curious about this.