AutoClick Pro news & patch notes

Ok so I managed to get this all done. It was a bear and I stayed up later than I probably should have some nights lol. With that said I'm tired boss. I think with everything I have done the last couple weeks I need to focus on any bug fixes that may arise for a while. Below is all the work that I have done for this release. New • Controller Mapper. Map gamepad buttons to your saved Auto Clicker, Macro, or Script profiles, the same way the Mouse and Keyboard Mappers work. Adding a mapping asks you to press the button you want. Bindings save as named mapping profiles with a master Enable switch. A button can also send a plain mouse click or key press instead of running a profile. Both modern gamepads and older DirectInput pads are supported. • Stick mouse control. Move the cursor with the left or right analog stick, with sensitivity, deadzone, and invert options. • Background mode. A tray icon lets you minimize to the tray, start minimized, and quit. Global hotkeys keep working while the window is hidden. • Adjust Monitor Access. On Wayland, a toolbar button lets you change which monitors cursor tracking may read. Multi-monitor users can share the full workspace. • Multi-monitor support has been added. On Wayland: clicking and cursor movement now reach every monitor, and macro recording and playback work correctly across screens. This one was a pain, but everything seems good after testing. • Switching tabs with unsaved profile changes now asks whether to save. • Windows: fixed a broken layout in the controller binding window and white flashing when adding mappings.

1.2.0 is now on the development branch for testing. It's not the default version yet since I want to test it thoroughly first before setting it as the new release. Hopefully by the end of the weekend I can release it. I have been working hard this week to get it ready so I can take my time with testing once Friday hits. What's new: - Controller Mapper: bind controller buttons to your auto clicker, macro, or script profiles, or to a mouse click or key press. - Stick-to-mouse: move the cursor with an analog stick. - Background/tray mode, with a minimize-or-quit prompt when you close the window. - Multi-monitor fixes and improved controller support.

I thankfully had a very good weekend working on this and was able to get the update out sooner than I would have thought. (My original estimate was about a week). I probably stayed up a little to late some nights, but I was really excited to get this done and to keep working. I hope everyone finds the new features useful. The two biggest additions in this update allows someone to map mouse and keyboard buttons to the profiles they have created under the tools. That way you can have multiple actions easily mapped across both mouse and keyboard. The Mouse Mapper and Keyboard Mapper also have the ability to save profiles as well. Which means you can easily select a profile based on what game it has been setup for. I also added a pause feature so that anything running can be suspended and resumed just in case it needs to be stopped for a moment. I also fixed some minor bugs as well which can be viewed in the change log if anyone is curious. With that said I hope everyone enjoys these updates!

Hello Everyone, I have started a development branch for version 1.1.0. This will be used to add the features requested by the community. Right now this is what I will be working on based on your feedback. Mouse button mapping for macros: This will allow the mapping of specified mouse buttons to recorded and saved macros. Keyboard mapping for macros: This will follow the same concept as the mouse mapping for macros, but of course will be for keyboard buttons. Pause and resume for macro playback: This will allow the pausing of macros in case they need to be suspended for some reason. After that they can be resumed from where the macro left off. I have already started work on this and hope to get these out as soon as possible. Thankfully this first set of features should not be too hard to add with how the base tools are built. It should just be a simple addition for each. We will see though since sometimes you never truly know until you get into the weeds of it. Everyone should have access to the development branch if they ever want to try it out. Keep in mind though that I will be pushing updates to the development branch basically whenever I have the time. Which means it is not obviously stable and could change at a moments notice. Once I have all these new additions ready I will test as thoroughly as possible before pushing it to the default branch for all users. Also, thank you all so much for the support! The response from you all has been very positive and I look forward to adding more to this application!