This is a change in the understanding of MHEG-5 and I don't think that you
could specify such change without loosing MHEG-5 conformance.
>3) Emmanuel's proposition
>This proposition is to generate a EntryFieldFull each time the numbers
>of chars are equal or greater than MaxLength. This allow a better control when
>overstepping MaxLength. More events are generated. I attach a document
>with
>some
>examples of engine behaviour with the actual specification and with this
>proposition.
>I think this modification should be add in the corrigendum.
I agree with your document on my proposed behavior side but I'm pretty sure
it won't be accepted because it is a technical change.
I don't agree with your Actual specification in 2 case because you suppose
your proposed correction above, which is not how I understand MHEG-5. To
me, when length was 3 and becomes 2 due to Delete user entry (so not by
setData), an EntryFieldFull event should be generated according to the
terms used in current version of MHEG-5.
>4) Not generate EntryFieldFull event
>The MHEG-5 IS says : "A SetData action should not generate
>EntryFieldFull
>event."
>
>I suggest to add : "A SetInteractionStatus action should not generate
>EntryFieldFull event."
>This is to avoid confusion : when the interaction is set
>(SetInteractionStatus(,True)), if nb of chars in TextData are greater
>than
>MaxLength, EntryFieldFull event is not generate.
I think this clarification is not problematic but I guess it will be
considered as useless because of the following:
When interactionStatus change, the number of chars is not change so it
cannot reach MaxLength at this time.
>5) Chars over MaxLength.
>What is the behaviour when user input char over the MaxLength limit ?
> 5.1) When a char is input, TextData is modified. The number of chars
>could
>be greater than MaxLength.
> 5.2) When a char is input, TextData is not modified.
> 5.3) When a char is input, TextData is modified but visual
>representation
>is
>limited by MaxLength.
To me, 5.1 apply. It's up to the author to manage this. At least, it has
always been the kind of answer I got here.
>6) MaxLength < 0
>This case is the same as MaxLength = 0.
This case is not specified and should be forbidden IMHO. Like this, if an
author specify a negative value, it would generate an error and MaxLength
would gets its default value which is 0, meaning that no specific MaxLength
was specified.
Best regards,
Emmanuel
__________________________________________________________________
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