- Eventscripts download mousedown portable#
- Eventscripts download mousedown code#
- Eventscripts download mousedown windows#
Eventscripts download mousedown code#
Updated code so acConsumePhysicalInput consumes all input, regardless of whether the stroke button is still held or not.Added dwExtraInfo to acMouseMove and acMouseClick for S+ to distinguish its own mouse event injections from others.Put the gwd variable back in.must've accidentally removed it in 2.1.51 (best guess).Mirrored 2.1.53's code change in the keyboard hook as well.
Eventscripts download mousedown windows#
Updated setLastActive (internal function) to also not consider the acDisplayText nor Settings windows a valid top-level window for which to set focus.
Passing 2 presses the Alt key temporarily during the SetForegroundWindow call (a known hack/workaround). Passing 1 uses a method which calls AttachThreadInput to temporarily bind S+ to the target window. Passing 0 uses the default SetForegroundWindow call. This allows you to try different methods of activating a window since Microsoft has made it very difficult. Added a new parameter to the end of acActivateWindow named method. Added code to change any pure white color passed into acDisplayText to 254,255,255 since pure white is the transparency color key. Removed duplicate gsx declaration in gestureComplete function (internal). If a gesture is completed and state 1 and state 2 are both executing, the gesture will be discarded if you have Play Sound For No Match checked and a WAV file selected, it will be played when this condition occurs to let you know it was ignored. Again, it's a compromise to keep some level of functionality prior to this change, even though it led to crashes. For the most part, no one will likely be affected by this change, and those who are will likely understand this contention and the necessity for it. Lua state 1 is always the primary state used for actions, state 2 is only used if state 1 is currently executing a script. For example, if you define a global variable named MyGlobalVar in the Global Lua tab and set it to 123, it will be 123 for each state initially, but if you fire an action which sets MyGlobalVar to 321 within a script that is still running while you execute another action which sets MyGlobalVar to 456, in Lua state 1, MyGlobalVar will be 321, but in Lua state 2 it will be 456. However, since these are separate states, they won't share the same values assigned to variables. Now, only two actions can fire simultaneously, each with their own state. This was only noticable when firing two actions back-to-back which had calls to acDelay (for the most part) leaving the Lua state unstable if another action fired in the same state, which caused S+ to crash. This is a compromise to allow some level of multi-threading, but preventing S+ crashes when actions were tripping over each other. Created an additional Lua state (total 2) and prevent more than 2 actions from firing concurrently. Added acSetKeyboardHook(0 or 1) to turn the keyboard hook on (1) or off (0).this is only for troubleshooting scripts so you can use the keyboard if S+ crashes to close the program. Eventscripts download mousedown portable#
Version history for StrokesPlus 64-bit Portable
0 kommentar(er)
