> it's just a regular window, and docking is disabled. Ok, that definitely lessens my concerns over the authoring environment tracking it in some way (lessens, not removes ;) ).
> i've noticed this behaviour before, but now it's especially > anoying because the window is playing back a large > quicktime. you can imagine what happens if director tries > to play 10 of those. For the sake of debugging, have you tested this without QuickTime in the mix? I'm just wondering whether all this opening/closing/forgetting is causing problems due to the player's windowing code or if there's additional complications related to the media involved, in this case, QuickTime. Just wondering, I know that's a side-track from your project and its goals but the troubleshooter in me has to ask... :) I still think it's worth testing with just simple windows so in order to make as similar a test case as possible, can you describe how often the window is opened and accessed in a given movie playback session (not a Director app session!)? Can you indicate how many times you must play your movie and/or open this MIAW before you start to see sluggish behavior? Can you give an overview of how much imaging you're doing? I'm hoping to make a basic test case and let it run on a spare machine to see what happens then float the results by our QA team for assessment. > the reason i need this window, is that i want to access a > quicktime movie's image with lingo. as far as i know, this is > only possible by copypixel the image of the stage, of the > MIAW in which that quicktime is running. (with DTS disabled) > if ther is another solution to do this, it would help me get rid > of the miaw at all. You are correct in that the way to image a playing QT movie is to have it on stage as a non-DTS sprite, then grab the image of the stage containing that sprite. You might also consider playing with the window's rect and drawRect (stage or otherwise) to have the video on stage yet clipped from the window viewport similar to how I've done it here: <http://poppy.macromedia.com/~thiggins/articles/videotextures/_archive/i ndex.htm> The above is an example of using QT imaging to render the video's image as a texture in a simple 3D scene. Since MIAWs aren't supported we must use techniques that allow the video to be on stage yet hidden from the user's eyes. Try something like that if you need an alternative. Although given that the problems you're citing pertain to author-time woes I don't know that it'll be worth the dev hassle as the end user won't notice this issue anyway. But obviously that's up to you, I hope this helped somehow. Cheers, Tom Higgins | Product Manager | Director & the Shockwave Player Adobe Systems Incorporated http://weblogs.macromedia.com/thiggins/ ... [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
