EventGhost

I like the new test button.
Is it possibly to test the whole macro? ;ore complex macros often need the complete list of actions.

I don't know if this is a good idea. Adding another button for "Test Macro" would be to cluttered. Making it the only option wouldn't be what the user wants in all situations.

For FindWindow actions you can already execute the FindWindow first and then take a MoveWindow action and test the settings, as the last found window will be targeted.

And here we are back on the question if it wouldn't be better to include the FindWindow into all window actions as a "WindowPicker". Most new users have problems to find out, that you have to use a FindWindow before any window action, if one would like to target a specific window.

The main reason why I haven't implemented it this way was efficiency considerations (doing the whole enumeration again over and over would take CPU cycles). But I think this could be optimized. First it could find out if a target configuration is actually the same as another (FindWindow is already doing it to compile its settings into a more efficient manner on load of the action) and then just skipping it, if there is no change. A second optimization could be archived if the Task plugin would go into the core, as this way EG can monitor the creation and deletion of windows and therefore skip a lot of computation.