On 11/4/12 3:16 AM, "Om" <bigosma...@gmail.com> wrote:
> On Tue, Oct 23, 2012 at 12:12 PM, Alex Harui <aha...@adobe.com> wrote:
>
>> Also, Stage3D isn't in the display list, so other visuals can't be put
>> behind it.
>>
>>
> I ran into this issue pretty quickly. Right now my frame of mind is to
> create a component with backgroundAlpha set to 0. There could be a way to
> selectively mask out areas on a flex application where we want to show
> Stage3D/Starling objects.
Yup, masks and backgroundAlpha=0 and other tricks can poke a hole, but add
complexity. Think of how much trickery is required to display a chart in a
popup! Is Stage3D so much faster that you really need that complexity? Or
is it the Charts ActionScript code itself that is too slow? Does [render]
really show up in the profiler for a Chart?
You also have the option to constrain the use case to scenarios that don't
have any chance of overlap like individual mobile app screens where things
generally don't popup (well, maybe they do on tablets...).
> Long term, we might have to fiddle with
> SystemManager to handle DisplayObjects and Stage3D objects seamlessly so
> that they dont overlap. I have no idea if this is possible or not. Any
> thoughts?
It is probably possible, but may not be practical in the general case. I
think you'll run into edge cases that are really hard (dropshadows from
components alongside the chart that overlap it slightly).
>
>
> And I think you have to handle interaction differently.
>
>
> I havent gotten to adding interactions. I guess you mean tooltips,
> datatips, etc. If not, can you please elaborate?
Yeah, like datatips. I haven't used stage3D myself, but I think the mouse
event model is different there.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
