I doubt if anyone is interested in this, but I have some additional details that I'll record here just in case someone needs it someday.
It appears that if the content of a TitleWindow exceeds the boundaries of the content area that the content area is filled with the background color after the borderskin is drawn. Forms sized at 100% seem to be very aggressive in taking up all available space, so it's possible that using a Form sized at 100% could cause the condition where the content area is filled with the background color after the borderskin is drawn in some situations (such as during a "Move" effect). The solution appears to be to set the backgroundAlpha for the TitleWindow to zero. This way if the background color fill is triggered after the borderskin is drawn it will not wipe out the content area background drawn by the borderskin. Of course if the borderskin does not draw in the content area, then this problem may never occur. I'm not sure why PopUpManager.centerPopUp and/or the "Move" effect triggers the background color fill because it doesn't in all cases. Regardless, setting backgroundAlpha to zero seems to solve the problem when it occurs. --- In [email protected], "Paul Whitelock" <[EMAIL PROTECTED]> wrote: > > Well, I think I've solved one part of the problem and stumbled into > another. > > I looks like PopUpManager.centerPopUp is causing the problem with the > background color fill. I create the TitleWindow using > PopUpManager.createPopUp and then right after that I call > PopUpManager.centerPopUp. A bit later in the code is when I execute > the Move animation. > > If I remove the call to PopUpManager.centerPopUp then the custom > content background is drawn. If I leave centerPopUp in, then the > content area is filled with the background color. > > The new problem is that the FormItem labels for the Form in the Window > disappear when the Move animation is performed (the form fields are > still there). Programming is fun, isn't it? :-) > > Paul > > > --- In [email protected], "Paul Whitelock" <news@> wrote: > > > > I have a TitleWindow that uses a BorderSkin (based on HaloBorder) to > > draw a custom background in the window's content area. The skin works > > fine until I try applying a "Move" effect to the TitleWindow. > > > > What happens is that when the move begins from offscreen top, the > > TitleWindow's content background is filled with the background color > > and the background generated by the BorderSkin is not displayed. Once > > the move has completed (the background color still fills the content > > area) if I display another TitleWindow that uses the same skin, the > > custom background is suddenly displayed in the TitleWindow that was > > moved (probably due to an invalidateDisplayList call). > > > > I tried changing the "Move" effect to a "Zoom" effect and the problem > > does not occur (the custom background is correctly displayed in the > > TitleWindow content area). > > > > I've put trace statements in the BorderSkin code and the custom > > content area background is being generated and drawn, so the only > > thing I can think of is that something is filling the content area of > > the TitleWindow with the background color AFTER the BorderSkin code > > executes. > > > > Anyone have any ideas about what might be happening and how to make it > > stop overwriting the content area background? Thanks! > > >
