You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently after issues I have experienced from 5.2.3.0, I reverted to 5.2.2.0
I noticed lately, when booting, that the LittleBigMouse icon will be green when started, but after a minute or so when booting is done, it will be blue. Figured something was causing that. I havent used this software long enough to know how it behaves.
But I set a 2 minute delay on LittleBigMouse from task scheduler, and it stays green after boot.
My thought is that, if any of these current issues could be fixed by adding a delay start, it would be worth a looking into?
Just trying to help.
(Listed all apps running at boot that might possibly conflict in some way. Might be wrong on some, but all involve overlay or pop up menus or desktop interaction if that makes sense.)
The text was updated successfully, but these errors were encountered:
Recently after issues I have experienced from 5.2.3.0, I reverted to 5.2.2.0
I noticed lately, when booting, that the LittleBigMouse icon will be green when started, but after a minute or so when booting is done, it will be blue. Figured something was causing that. I havent used this software long enough to know how it behaves.
But I set a 2 minute delay on LittleBigMouse from task scheduler, and it stays green after boot.
My thought is that, if any of these current issues could be fixed by adding a delay start, it would be worth a looking into?
Just trying to help.
Conflicting apps could be between:
DisplayFusion, Dual Mouse Tools (DMT), PowerToys (FancyZones), HideVolumeOSD, ModernFlyouts, Blacktop, QuickLook, FlowLauncher, WinDynamicDesktop, F.lux, NZXT CAM, Twinkle Tray.
(Listed all apps running at boot that might possibly conflict in some way. Might be wrong on some, but all involve overlay or pop up menus or desktop interaction if that makes sense.)
The text was updated successfully, but these errors were encountered: