God, what a disaster. I'd say the right thing to do would be to add the
mask directly to the media container, but we rely in a few places on being
able to easily decorate the media container by winging other objects off
the edges, and we don't want to just create one mask that's big enough for
the user media as well as our decorations (because then malicious user
media could alter what the user perceives as our decorations).
Perhaps the right thing to do is make MsoySprite not be a subclass
of MediaContainer, but contain one. That's a refactor I won't be
rabbit-holing right now, thankyou.
git-svn-id: svn+ssh://src.earth.threerings.net/nenya/trunk@176 ed5b42cb-e716-0410-a449-f6a68f950b19
pixels so that I'd receive mouse clicks. While contemplating how bitchy
to be in my check-in comment, I wondered why I hadn't needed this when
the video was hosted inside a MediaContainer. It occurred to me that perhaps
the mask was helping, and sure enough: a sprite's mask helps define the
bounds of the sprite for mouse event purposes.
That's really good to know. I'll have to experiment further.
So: set up a mask on the VideoDisplayer, for no other reason than to
be informed of mouse events in all cases.
git-svn-id: svn+ssh://src.earth.threerings.net/nenya/trunk@175 ed5b42cb-e716-0410-a449-f6a68f950b19
Ray Greenwell