Time.timeScale=0 breaks the buttons

[Devil_Inside]

Setting Time.timeScale to 0 on a button press, will freeze that button in the Hovered state, and will make that button "selected", so you can't press any other button while timeScale remains set to 0.
To reproduce:
1. Create a new Scene and add a new 2D UI,
2. Add 2 buttons to the panel: Button1 and Button2
3. Add a script that simply sets Time.timeScale=0; as the "OnClick" target for Button1
4. Add a script that prints "Hello" to console as the "OnClick" target for Button2
5. Run the game, click Button1 to "stop" the time.
6. If you try to click Button2 now, you'll see that it doesn't respond, but instead Button1 is being clicked.

[JMab]

I noticed that too. I think it would be good if all of the NGUI classes used the Realtime object for timing.

[ArenMook]

Looks like I broke it recently. You can fix it by adding the following code to the beginning of the UICamera.ProcessMouse function:

1.                 if (Time.timeScale <= 0.25f)
2.                 {
3.                         if (!Raycast(Input.mousePosition, out lastHit)) hoveredObject = fallThrough;
4.                         if (hoveredObject == null) hoveredObject = genericEventHandler;
5.                         for (int i = 0; i < 3; ++i) mMouse[i].current = hoveredObject;
6.                 }

[Devil_Inside]

Thanks!

[wom]

Argh!  I just spent ages tracking this down.  And the worst thing is - I scanned this topic only a day or two ago, just didn't process what I was reading properly.  How embarrassment 

[Eugene]

Thank YOU, ArenMook!
You just made my day. I was bummed out it didn't work, and I'm so glad I found your solution that fixed this problem almost instantly, that I've registered on this site just to tell you how grateful I am for this!
I probably would've spent up to a week fixing this on my own. Well done, sir, well done!

[Holdwick]

Thanks so much!