[Bug] Can no longer use user interaction as trigger in newer version about screentogif

[MichaelWoodc]

In multiple acts of hopeless desperation, as I had to complete everything quickly, I enabled developer mode. This seems to have made it work for my use case.

Can anybody confirm this is the only required change to capture user events inside vms and protected windows? If not I'll go over everything I tried

[MichaelWoodc]

Ok I just updated to vmware 17.5 and I now have the same issue. One thing I had done on my previous VM was I enabled hyperv after having vmware installed. When I updatd, I was greeted with tthe following screen:

I think that this feature is what disables it from being able to detect the clicks. Not sure though.

[NickeManarin]

Hello Michael!

ScreenToGif needs the OS to report the clicks or else nothing can be done.

If the clicks are not being registered (or are being done in a admin-run window, I simply won’t receive them).

[MichaelWoodc]

Hello Michael!

ScreenToGif needs the OS to report the clicks or else nothing can be done.

If the clicks are not being registered (or are being done in a admin-run window, I simply won’t receive them).

Thanks for the response! I am not sure what I did, but somehow, I got it to work again. I had to downgrade vmware, and I did so many things but it wasn't working. After restarting my PC it worked fine.

So it's obvious to me it's not a bug at this point. I love the program! If only I knew enough about this kindof programming to contrubute and make it seamless for these very rare use cases lol. Thank you!!

[MichaelWoodc]

I think the trick is to actually run screenToGif as admin, AND for some reason the other app had to be run as an administrator, then it could capture mouse clicks. Hope this helps anyone trying to grab user events from inside a "protected" app! (You won't be able to capture keystrokes though a VM, clicks only, there's lots of VM isolation going on)

2024-01-06.18-04-38.mp4