Loss of mouse control - odd behaviour

[tempest8008]

Good morning.

To start I'm VERY new to MiniMouse.  
I am a competent scripter.

My concern is the actual program itself.  Right now I have an exceedingly simple macro running that is simulating mouse clicks.
It right clicks, waits a few seconds, then right clicks again, pauses, then repeats.  No big deal.

However I have noticed the program suddenly 'stutter' sometimes and break the flow of the macro.
When I use the hotkeys to stop the macro the application appears to lock up.  I can't click on anything unless I CTRL+K to kill the application.
When I go looking the system tray I see half a dozen MiniMouse icons in there.  They disappear as I hover over them.

If I leave it alone, eventually I get mouse control back.

OS is Window 10 Pro.
With my application running as well as MiniMouse I'm using less that 25% CPU and memory.
I have the debug log off.

I'm wondering if there are any KBs I should or should NOT have in order for MiniMouse to work correctly?  Or .NET versions, things like that?

Thanks for any assistance you can provide!

[Steve]

Hi tempest8008

This is a little odd TBH. The 'stutter' shouldn't be occurring at all regardless of the complexity of the macro.
Are you running the latest version of MMM? If not then update. The latest version is built for .net 4.5.
The multiple icons in the system tray may be a bug from an much older version. It could also be that the app is not closing cleanly on it's own. How are you closing your MMM sessions off? Are you closing the app cleanly each time?
The macro locking up and requiring the ctrl+k is also strange.

Off the bat id be looking at your Win10 host. Do you have problems else where with your system? I mean, could this be caused by a failure somewhere in your system or something you've got running? I say this because a generic Win10 Pro OS running an .mmmacro that right clicks and pauses should just 'work'. Its leading me to think the environment it's running on is somewhat the issue here.

[Stefanie]

This has happened dozens of times to me as well. It seems to be a frequent problem with entire sequences messed up from the loss of 1 or 2 inputs.