I've run into a very similar thing when I switched to 2.4 and was
messing with it over the weekend.
I have found a workaround which seems to work ok, but I will still
report this as a bug.
The problem, I think, comes when the player checks its own size...and
it returns the size - the controller height...so when it sets the
rect of the new movie (I am assuming that you are swapping movies
into one player)...it sets it to the smaller size. Repeated calls
shrinks it by 16 or so pixels each time until you have a lot of very
short, fat people in your movie :)
So, a couple of things to try:
1. Do not call show player if the player is visible. It will cause
the player to walk down the screen. If lockLocation is on, this will
also shrink it. If this doesnt work, try..
2. Set locklocation to false, and set the fileName of the movie to
empty when you are done with it...and before you set the fileName to
something else. This seems to alleviate most size reporting bugs.
BUT, it can cause flashing.
-ml
>
>
>Ken Ray a �crit:
>
>> Did you set the lockLocationi of the player object to true?
>>
>
>I tried both options (true & false), among many other things
>(like setting the filename of the player, as well as its height &
>width every time I want to start it), but problem remains...
>
>BTW I forgot to mention that problem occurs not only with
>.mov files, but also with .swf...
>
>Thanks.
JB
--
Mark J. Luetzelschwab [EMAIL PROTECTED]
Texas Center for (v) (512) 232 6034
Reading and Language Arts (f) (512) 232 2322
http://www.texasreading.org
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
