Sure, try http://www.symetri.com/flex_test/test.html <http://www.symetri.com/flex_test/test.html>
If you use the vbar to scroll up/down you should see what I'm talking about -- the form content gets messed up. Then, if you roll the mouse around the VBox after scrolling it usually refreshes the item as you roll over it, causing it to "jump" as it shifts from the jumbled position to the actual position. I've even seen it where the buttons are totally gone and then you roll the mouse over and they suddenly reappear. While putting together is test case, I figured out the source of the problem. I had added "wmode","opaque" to my AC_FL_RunContent in index.template.html. On the actual site/project I've added more stuff, but for this test case I used the base index.template.html and only addded that one line (after I figured out that was causing the issue). I added the "wmode","opaque" for a reason (to fix a previous issue) -- I just can't recall what that issue was. I hesitate to take it out, but I might not have a choice. Any reason this change to AC_FL_RunContent would be causing this issue? --- In flexcoders@yahoogroups.com, "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Can you post a simple test case? > > > > ________________________________ > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of byte.sensei > Sent: Tuesday, January 08, 2008 10:28 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] VBox content not refreshing on scroll > > > > I've noticed in several places that when scroll bars are used that the > content in whatever component is being scrolled doesn't get updated. > > I have several different Canvas and VBox/HBox screens with a vertical > scroll bar, and when you scroll up and down it seems to "jumble" up the > content and even after you stop scrolling the content remains jumbled -- > like it needs to be refreshed to draw everything in the correct > positions. > > I'd really like to understand *why* the content isn't keeping up with > the scroll and ends up all jumbled up. Of course I'd also *really* > like to know how to fix this issue... >
