shuko 59 Posted June 13, 2010 Let's have a race. Winner will be the person who is first to find out how the command setTaskResult actually works. Go! Share this post Link to post Share on other sites
Big Dawg KS 6 Posted June 13, 2010 Well, I assume state would be one of the following: "Succeeded" "Failed" "Canceled" "Created" "Assigned" As for what the command actually does, no idea. I guess we'd have to figure out what result is first. Share this post Link to post Share on other sites
Jelliz 10 Posted June 13, 2010 you could try to use taskResult task to find out? Share this post Link to post Share on other sites
shuko 59 Posted June 13, 2010 tsk setTaskResult ["succeeded","hep=true"]; taskresult tsk gives the exactly same array: ["succeeded","hep=true"] Share this post Link to post Share on other sites
rübe 127 Posted June 13, 2010 soo, setTaskResult is something like an eventhandler for tasks, so that in your example hep would be set to true once the state of tsk has changed to "succeeded"? That's what it's for? Seems to be pretty useless then, since you have to change the task's state anyway at some point, so why not put your result-code there too? Share this post Link to post Share on other sites
Jelliz 10 Posted June 13, 2010 very useless if im not missing anything obvious, you can just use task taskstate "SUCCEEDED" in combination with task settaskstate "SUCCEEDED";. Share this post Link to post Share on other sites
shuko 59 Posted June 14, 2010 I'm looking to find out what it does/how to use it, not how NOT to use it. Share this post Link to post Share on other sites
st_dux 26 Posted June 14, 2010 Ruebe appears to have the most likely explanation. Share this post Link to post Share on other sites
shuko 59 Posted June 14, 2010 Ruebe appears to have the most likely explanation. Yeah, "appears". However, the command doesn't work like that. I've tried to give a string and code to it, but it doesn't do anything. Nor does it give any error either. Share this post Link to post Share on other sites
st_dux 26 Posted June 14, 2010 Honestly, I think it's just a broken command. They were probably planning on using it for something, but then decided to go in a different direction. There are a few other examples of this in the biki as well, e.g., agent. Share this post Link to post Share on other sites