Author |
Topic |
|
Hax
128 Posts |
Posted - 02/07/2012 : 22:59:54
|
For instance, acSendKeys("{Enter}") without quotation marks i.e. acSendKeys({Enter}). |
|
Rob
USA
2615 Posts |
Posted - 02/08/2012 : 01:32:09
|
There's definitely a shortage of error handling and it's something on my to do list. |
|
|
Rob
USA
2615 Posts |
Posted - 02/08/2012 : 16:38:45
|
Fixed this for acSendKeys in 1.4.9.
Will work through all of the actions and add parameter type checking..gonna take a while, but 1.5.0 should completely resolve invalid action parameter crashes. It's really bad when S+ crashes, huh?! I tested your scenario, talk about bringing the system to a screeching halt. |
|
|
Rob
USA
2615 Posts |
Posted - 02/08/2012 : 18:18:23
|
Added parameter defaulting to all actions. Instead of checking the potential combinations of parameter conditions, defaults are assigned to eliminate crashes.
For example, specifying acSendKeys({Enter}) will simply do nothing, since the parameter is not valid, but S+ will not crash. It will simply become the equivalent of acSendKeys("") since a string wasn't passed in.
For some action parameters, defaults are set to something which makes sense, like if a non-string is passed into acDisplayText(), it will default to "Arial", not an empty string, etc. |
|
|
Hax
128 Posts |
Posted - 02/09/2012 : 00:08:52
|
quote: Originally posted by Rob
I tested your scenario, talk about bringing the system to a screeching halt.
I additionaly tested this bug on a Windows XP virtual machine and it handled crashes so much better than Windows 7. No damn freezes. Thankfully it's fixed now. |
|
|
|
Topic |
|
|
|