- From: Dana Rosenfeld <Dana.rosenfeld@emblaze.com>
- Date: Sun, 26 Jan 2003 21:16:51 +0200
- To: <www-smil@w3.org>
- Message-ID: <980C7B879697C7448A54C9B065AAFAAC060D08@embexcil01.emblaze.ent>
Consider this SMIL source: <smil xmlns=" http://www.w3.org/2001/SMIL20/Language"> <head> <layout> <root-layout id="viewport-0" title="viewport 0" backgroundColor="black" width="400" height="400"/> <region id="r1" left="0" width="400" top="0" height="100"/> <region id="r2" left="0" width="400" top="100" height="200"/> <region id="r3" left="0" width="400" top="300" height="100"/> </layout> </head> <body> <par dur="30s"> <img id="bar" region="r1" dur="30s" src="../images/frown.jpg"/> <img id="foo" region="r2" begin="0;bar.activateEvent+10;joe.activateEvent" dur="8s" end="bar.activateEvent+11" restart="whenNotActive" src="../images/smile.jpg"/> <img id="joe" region="r3" dur="30s" src="../images/frown.jpg"/> </par> </body> </smil> Now, lets say that the user clicks on bar at t=2s and then clicks on joe at t=9s. How is the player supposed to react? Since activating bar can either begin or end foo - we should check foo's state on t+10. At first (before the user clicks on joe), it seems that we should consider the first click as a begin trigger. But then comes the second click, and so the logical approach is to change the first click to be considered as an end trigger. BUT, it doesn't make any sense! Do I have to keep a list of all "doubled" events, in case that the user behaves like that? It seems to me very clumsy. Can't I just consider the first click as a begin trigger and when the second click comes (t=9s) - restart foo and and end it after 8s? (since I won't be able to restart foo again) thanks, Dana Rosenfeld ************************************************************************************************** The contents of this email and any attachments are confidential. It is intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to any one or make copies. ** eSafe scanned this email for viruses, vandals and malicious content ** **************************************************************************************************
Received on Sunday, 26 January 2003 14:17:30 UTC