Author |
Topic |
|
Rob
USA
2615 Posts |
Posted - 03/06/2016 : 22:43:37
|
64-bit:
Setup Package - Signed, Win Vista through Win 10 (recommended)
Setup Package - Unsigned, Win XP through Win 10
Portable/ZIP - Signed and Unsigned
32-bit:
Setup Package - Signed, Win Vista through Win 10 (recommended)
Setup Package - Unsigned, Win XP through Win 10
Portable/ZIP - Signed and Unsigned
Notes: - Updated gGestureComplete to support queueing during mouse wheel firing events instead of discarding the events when both Lua states are executing - Added acSetNumberVariable/acGetNumberVariable and acSetStringVariable/acGetStringVariable actions. These actions allow you to store and retrieve number or string values in a key/value pair form. These value maps persist as long as S+ is running, unlike Lua variables which are cleared anytime the Lua engine is reloaded, which happens when you tell S+ to reload the Lua engine or when you click OK in the main S+ screen. Also, these value maps are shared across the 2 Lua states active in S+ at all times, so you can be sure the stored value will always be persistent and accessible so long as S+ remains running. Note that the number and string maps are independent, so you can use the same variable name in each, as in the example below, they wouldn't overwrite the other. Example usage: acSetNumberVariable("Test", 5) acGetNumberVariable("Test") --returns 5 acSetStringVariable("Test", "Hello world!") acGetStringVariable("Test") --returns "Hello world!" |
|
|
Topic |
|
|
|