Alex Hill wrote:
I have a question about the synch points for gestures.The current sync code is buggy. It was originally written for very early version of BML (pre-ISI Twiki). And while pieces of it have been adapted, it needs a total overhaul. Something that is high on our list after we get out of demo season. That said, it should support constraining most behaviors (except gaze) to any pair of start/ready/stroke/relax/end sync-points (note, stroke_start and stroke_end were added later, and are not very well supported by SBM). Given more than two of those, it picks two in this priority: stroke, ready, relax, start, end. However, that selection is an ugly if/else if/else if tree. Many (most?) of the conditions have not been rigorously tested. I'd like to hear suggestions on how this scheduling can be tested in a manner applicable to future implementations. I have a feeling I need to log the resulting schedule of any BML request. If I output this data back to ActiveMQ / VHMsg, I could not only implement some sort of test framework, but also provide a runtime visualization of the schedule, useful for testing and understanding the BML behavior-track synchronization model. Any takers? Anm |
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Smartbody-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartbody-developer
