I think your question and your problem is specific on how the platform will
handler user interaction, especially for entryFields.
>here is another technical question, this time about the Interaction
>Status.
>
>It is written in 41.1 2c in case of a
I think it's rather in 41.4 2c for others.
>SetInteractionStatus(false) action:
>"...generate the InteractionCompleted Event"
>
>How about removing this sentence?
>
>
>Reason: For example, you have an Entryfield, which is interactible. With
>some means the user terminates this interaction, I would expect the
>Entryfield to generate a IteractionCompleted Event on it's own.
Here my question is : how (with which means) will the user terminates the
interaction ? I think this is the source of your question.
> This
>event will be used by a friedly MHEG app to fire a link which sets the
>Interaction Status to false (which is the only way to change the
>interaction status). A second "interaction completed" it not that good.
>
In my understanding, with a platform that do not handle unspecified tasks
or events, I would expect that when the user have finished to enter chars
in the entryField, it terminates the entry with a specific userInput event.
Then this userInput event could fire a link the set the interaction status
to false and generates (but only once) the interactionCompleted event. All
the same, an EntryFieldFull event could fire another link that also set the
interactionStatus to false.
IMHO, it is rather the whole paragraph 43.3 4 which is confusing or should
be either removed or explained. What does it mean by "because the user
terminates the entry" ? It isn't said anything on how the user is supposed
to terminates the entry here or I perhaps missed something.
>
>Main issue behind: Who is in charge to generate the InteractionCompleted
>event? We suggest that it is comming from the EntryField object itself.
>
All can be discussed. I'm usually opened to all necessary changes,
especially when it allows to make things clearer for everybody.
>
>Additionally: In the same paragraph, it is missing that the interaction
>status should be set to false, if a appropriate action is executed.
I agree.
Regards,
__________________________________________________________________
Emmanuel BEUQUE mailto:ebeuque@pratique.fr
MediaServ tel: +33 (0) 2 99 64 35 64
Multimedia consultant & developer fax: +33 (0) 2 99 64 36 65