Author Topic: Since 3.4.3 UIPanel changes causing vertical scrollview items to disappear  (Read 4165 times)

kittikun

  • Newbie
  • *
  • Thank You
  • -Given: 2
  • -Receive: 5
  • Posts: 46
    • View Profile
When upgrading from 3.3.6 to 3.4.8, I found a very confusing problem about my scrollview items disappearing when you would reach a thirds of the list.

I managed to nailed it down to 3.4.3 UIPanel changes. I have looked at it but didn't managed to find the cause.

It happened in two different screens that had one thing in common, they were using a vertical scrollview.
I didn't managed to get exact reproduce steps but i you want, I might send you the scene in question in a private msg (the company won't allow me to make it public)


« Last Edit: February 06, 2014, 09:05:15 PM by kittikun »

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Since 3.4.3 UIPanel changes causing vertical scrollview items to disappear
« Reply #1 on: February 06, 2014, 10:05:22 PM »
If you have widgets directly underneath the scroll view (as children), then those widget's dimensions are used to determine the clipping region. Even if their sub-children happen to extend beyond that region. Since people keep running into this, I'm going to remove this.

kittikun

  • Newbie
  • *
  • Thank You
  • -Given: 2
  • -Receive: 5
  • Posts: 46
    • View Profile
Re: Since 3.4.3 UIPanel changes causing vertical scrollview items to disappear
« Reply #2 on: February 06, 2014, 10:21:25 PM »
Thanks for your quick reply

Yes we are doing it like in the example scene 7 - Scroll View (Panel)

Scrollview
 |
 |- Container (Grid or Table)
      |
      |- Sprite child
      |- Sprite child
      |- Sprite child
      |- Sprite child
      |- Sprite child
      |- etc..

One difference with your scene is that our panel is size is set to be exactly the clipping region whereas your encompass all the items. Since the generate items dynamically, we cannot predict the final size but I suppose it could be possible to use NGUIMath.CalculateRelativeWidgetBounds