Author Topic: UIGrid strange problem  (Read 1534 times)

netlander

  • Newbie
  • *
  • Thank You
  • -Given: 2
  • -Receive: 1
  • Posts: 11
    • View Profile
UIGrid strange problem
« on: December 01, 2014, 04:53:32 AM »
Hi Arenmook,

We have an implementation of a board using UIGrid composed of a number of nodes with colliders attached to them and we are intercepting click and drag events to move, add and remove items to the UIGrid.

The board plays well enough for a reasonable amount of time then it freezes and it seems that the events on the grid are not being triggered.

At this point we are thinking that this problem only happens on Android devices as it has not been possible to replicate inside of Unity and it takes a large number of moves before the freeze.

We have ensured that the colliders are not overlapping and that they have a larger depth (z > 1) and also the widget depth of the nodes is in front of everything else. Now we have run out of options to try.

So the question is are there any obvious reasons why the UIGrid will seize up like that and we would appreciate any advise for which direction we should be looking to investigate this weird problem (it's worth mentioning here that the rest of the UI in the level works fine after the freeze, we have buttons that still respond to clicks, etc...).

Thanks
Paul

NGui 3.6.7 (Unable to upgrade due to the fact that any recent version breaks the code).
Unity 4.5.5f1

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: UIGrid strange problem
« Reply #1 on: December 02, 2014, 11:28:15 AM »
'z' has no effect in NGUI by default, and should be left at default 0. Only actual depth value matters -- camera depth, panel depth, and widget depth.

You can enable Debug on the UICamera to see what's intercepting your events.

netlander

  • Newbie
  • *
  • Thank You
  • -Given: 2
  • -Receive: 1
  • Posts: 11
    • View Profile
Re: UIGrid strange problem
« Reply #2 on: December 03, 2014, 10:16:50 AM »
Even though we moved to a different implementation for the particular mechanic I have a feeling that there's a memory leak somewhere that causes the crash but that's just a hunch. Will investigate further if I get the opportunity (time).