Mini Mouse... code folder for consectutive 'Mouse Movements'

[ilcaa]

just started using program and i like it.. but scrolling and finding specific keys is annoying especially with all the mouse movement commands.  I understand the need , to .. make mouse movements precise as possible, but finding the basic, key presses, etc is annoying.

is it possible to 'code fold' consecutive mouse movement commands so the macro is reduced visually in the editor and easier to find things and and edit the macro?  maybe make commands other than 'mouse movement' as red so its easier to find

if there is a way please let me know.  thanks

[Steve]

Hi

Yes 'code folding' would be great and makes a lot of sense. It's not available at the moment and would require some reengineering of the main code list but is something i could look into for sure.

In the meantime there is sort of something that can reduce the amount of 'Mouse Movement' lines but it require manually entering in values. 

Consider this example:

1 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER%::1000
2 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER1%::600
3 | RUN ACTION | DEFINE INTEGER VARIABLE | %INTEGER2%::100
4 | RUN ACTION | MOUSE MOVEMENT | 100-100
5 | RUN ACTION | MOUSE MOVEMENT | %integer1%-%integer2%:%integer%
6 | RUN ACTION | MOUSE MOVEMENT | 100-150:%integer%, 200-240, 210-270:100
7 | RUN ACTION | MOUSE MOVEMENT | 300-350:100, 375-400:100, 425-450:100,475-500:100,525-550:100,575-600:100,625-650:100,675-700:100,300-350:100, 375-400:100, 425-450:100,475-500:100,525-550:100,575-600:100,625-650:100,675-700:100
8 | RUN ACTION | MOUSE MOVEMENT | 300-350:10, 375-400:10, 425-450:10,475-500:10,525-550:10,575-600:10,625-650:10,675-700:10,300-350:10, 375-400:10, 425-450:10,475-500:10,525-550:10,575-600:10,625-650:10,675-700:10

The 'MOUSE MOVEMENT' action accepts mouse movement X-Y:T (Mouse X position - Mouse Y position: Time Value) values separated by a comma (,).
Lines 1, 2, and 3 above declare some variables to use as an example however this is just a test using variables and obviously is not required.
Take line 7 above. We have 16 mouse movements here compressed into one line. There is a limit to how many you can have on one line. I think its a few hundred.

The problem with Mouse Movement is there is no graphical tool to add the entries in.  It will have to be done manually.  Originally I had built a graphical tool for the mouse movement action and planned to release it on the previous update however I had a few issues with the design. There is a problem, if you have too many mouse moments (something above 100) the macro line will not be visible in the macro list. It will play, but it wont be visible. You see why i left it out.

Anyway enough rambling from me lol