2.3QT Observations:
>> [1] Is there a memory overhead in not being able to purge a movie after
>> use, or is this a non-question?
>It's a real question, but may be a non-problem ;-) The player object
>purges the prepared movie if you close it (e.g., when you go to
>another card) or set the fileName property to empty. Under what other
>circumstances should it do this? Maybe when you hide it? But that
>might make hiding and showing slower...
I guess it depends on the impact _not_ purging has on program performance.
An "alwaysPurge" property, defaulting to true?
Note: AlwaysBuffer must be set to true for a video movie player to
show/hide correctly. This is implicit in the readme, but not stated
explicitly.
>> [2] Request:
>> If the callback message included the "time" parameter it would eliminate
>> the potential proliferation of callback message handlers required.
>Good idea. Maybe even better would be to accept a parameter with
>command? So the callbacks property could be something like:
>1234, mycallback cb1
>2345, mycallback cb2
>
>The parameters could only be fixed strings, though. Would this be
>better than returning the time, or just confusing?
Much better. In my experience, things are confusing only when not clear. If
the rule is "fixed string up to 255 chars" then that's what we abide by.
Perhaps the time should be returned by default (rather like "mouseUp" just
in case you need to know 1/2/3) if no other param is passed:
1234, mycallback cb1 -- would return the value of cb1
2345, mycallback -- would return "2345"
/H
Hugh Senior
The Flexible Learning Company
Consultant Programming & Software Solutions
Fax/Voice: +44 (0)1483.27 87 27
Email: [EMAIL PROTECTED]
Web: www.flexibleLearning.com
