VoxCommando
New Features and Feature Requests => Feature Requests => Topic started by: Haddood on March 30, 2016, 09:00:15 PM
-
based on this:
http://voxcommando.com/forum/index.php?topic=2552.0;topicseen
how about a variable {LastError} or something similar that give us access to the last error ... or copying the error to {LastResult}, or any other solution that you see fit
this will give us the chance to trigger events trying to remedy the problem ...
quick example, scrape something on local host, unable to connect to remote server, is an indication that The server might not be running ... try to launch it ...etc.
-
http://voxcommando.com/mediawiki/index.php?title=Logic_Block#LastActionSuccess
-
Nim5ter, I am aware of that ... Storing the error complement this ... And same command can return different errors which entails different actions ....
-
Based on the quick example you described the existing tools are sufficient.
Anyway this is a reasonable request and can probably be implemented without too many tears.
-
Based on the quick example you described the existing tools are sufficient.
Anyway this is a reasonable request and can probably be implemented without too many tears.
that is great news ... now I will ask in help on how to use the current tools :)
-
I've added the {LastInfo} variable in 2.2.1.7
http://voxcommando.com/mediawiki/index.php?title=ChangeLog#Version_2.2.1.7
-
James, u r the real terminator !!! ... Never cease giving best support ever !!!
Tx