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
This should be a fairly simple addition, as it will be just capturing the location information of the mouse X/Y coord and defining a new global shortcut to trigger the capture (that can be set in preferences) although the UI/UX of it will need some work.
This would encompass doing the following:
Mouse X/Y on mouse pressInput types should be stored and used if the user has pre-defined said input, if not it should default to the current mouse position at the time of the action being performed
Does this option require a checkbox or some form of sub-UI that only appears of the pressInput type is mouse on the input capture modal?
Pre-defined in this case would be manually editing two boxes that store the X and Y coordinates that the user can edit
Option to record a mouse point via a shortcut key defined in the app preferences, so the user moves the mouse to the screen postion then confirms it with the keyboard shortcut and its captured by the app and stored as part of the above process
This would just capture the value into the boxes above as to save additional processes
A simple UI button called 'record mode' or something could do this, with the shortcut key displayed underneath (like the stop watch buttons) in which pressing the button activates the listener and keyboard shortcut until the shortcut is pressed, in which it stops listening at the X and Y coordinates are recorded into the editable boxes
The text was updated successfully, but these errors were encountered:
If it's possible, I want suggest another feature to help the status reading:
When the program is in function, change the icon in the toolbar to instantly show the tool's status.
And last, but not least 😜, please add the possibility to set infinity click
As mentioned in #7 as part of this comment on a reference for chained actions, it would be handy for the user to be able to record or define the mouse action location ahead of time.
This should be a fairly simple addition, as it will be just capturing the location information of the mouse X/Y coord and defining a new global shortcut to trigger the capture (that can be set in preferences) although the UI/UX of it will need some work.
This would encompass doing the following:
pressInput
types should be stored and used if the user has pre-defined said input, if not it should default to the current mouse position at the time of the action being performedpressInput
type is mouse on the input capture modal?The text was updated successfully, but these errors were encountered: