|
7/10/2006 2:37:34 AM
|
Mario C
Posts 1
|
I just purchased the business version of “Macro Recorder” and have had great success with the program thus far but I am hoping it may be possible to add a new feature as I have a slight limitation?
There is a function within Macro Recorder (WAIT FOR WINDOW) but I need the further ability to watch for a sub window (within) that same program.
Macro Recorder seems to only access programs shown in the task bar by their title but not other window titles (within) that program that are not shown in the taskbar.
For example let’s say that I am automating a program the produces a ‘score’ or ‘result’ via a pop-up window that I need to be able to ‘detect’ and then automate further from.
Also, is there a way to have the program ‘sample’ in longer increments when using a (WAIT) command? For example, on my dual-core home system I notice that Macro Recorder uses one of the two processor cores at 100% while (waiting) and this greatly reduces the accuracy of a running program that is calculating a result. Is it possible to specify how often Macro Recorder will ‘probe’ for a time increment based on a (ms) or (second)? This way it will be far less strenuous on the processor resources.
Thanks much.
|
|
7/15/2006 4:23:56 PM
|
jitbit
Posts 712
|
Thanks, we have added this to our 2do list, will fix in the next release
|
|
7/31/2006 8:24:54 AM
|
willski
Posts 1
|
Just started using JITBIT Macro Recorder to automate some regression web tests.
Some of the macros that I record are quite long and on each occasion I edit them afterwards to reduce the Timeout (ms) for each keyboard stroke down to 20 to make it faster to re-run. One feature that would be useful instead of having to edit each Keyboard stroke separately would be a bulk edit of the Timeout fields so that a user can highlight a number of rows and then set the timeouts to the same value.
Thanks
|
|
2/8/2007 12:47:00 AM
|
Wolfgang
Posts 8
|
New feature wanted: I need to comment my long macros.
A new command "comment line" would be nice (actually I use the command "label" instead).
Column 6 would be nice to be editable to comment some clicks.
|
|
2/8/2007 12:56:55 AM
|
Wolfgang
Posts 8
|
Small but nice improvement would be: The column size of the macro definition should be saved.
|
|
2/8/2007 1:19:21 AM
|
Wolfgang
Posts 8
|
New timing feature would be nice. As the response time of a system depends on various facts, I need to be more flexible to define the delay. A command like "after window is active" or "after wait symbol disappears" would be helpful. As long as I start the macro from the editor window I can adapt the speed to "slow". Using an exe, I found no way to slow down the execution speed.
|
|
2/8/2007 2:55:48 AM
|
Wolfgang
Posts 8
|
An export/import in csv-format would be nice. So modification of the macro would be easier, e.g. for
- global replacement
- editing directly in the table cells, instead of open and close the dialog window.
|
|
2/8/2007 3:25:47 AM
|
Wolfgang
Posts 8
|
It would be nice to have some variables. All userinput could be given, directly after the macro has started. Then the macro could run to the end without interruption for inputs.
|
|
2/8/2007 4:13:54 AM
|
Wolfgang
Posts 8
|
A subroutine feature would be nice. Actually macro exe-files can be startet, but there is no feedback, when they have terminated. I could insert the "Wait for Input"-command, but that is not a realy comfortable way.
The macro recorder is very helpful for testroutines today. I think the macro recorder has the power to be a realy good tool for recursive testing in future.
|
|
2/9/2007 3:23:10 AM
|
Wolfgang
Posts 8
|
Nobody is perfect. The function "undo" would be nice.
|
|
9/1/2007 6:24:07 AM
|
fdragon
Posts 4
|
The funciont "and" would be nice too ^^
|
|
pages:
1 |
|---|