Example 3, OnHover problem when UICamera use Touch only

[yuewah]

In Unity Editor,

If I only checked UICamera's "use Touch" = true, UIButton does not receive OnHover event when I move the mouse cursor over it.

However, when I click on it, the UIButtonColor and UIButton Play Animation will receive OnHover event.

[ArenMook]

Hmm... there should be no hover events with the touch-only mode. I'll look into this, thanks.

[loopyllama]

that is because it is missing the mouse check before sending onhover. you have already posted this before...here is the old post
http://www.tasharen.com/forum/index.php?topic=441.msg2097#msg2097

once again, try this:
UICamera.cs line 896, change:

1. if (currentTouch.pressed == mHover)

to

1. if (currentTouch.pressed == mHover && useMouse)

[ArenMook]

This change went live a while ago.

[yuewah]

I am using 2.0.7c, and see the line of code. But it didn't fix it .

[yuewah]

UICamera.cs line 712

1. if ( !isPressed && mHover != null && mHover != mMouse[0].current)

to

1. if ( useMouse && !isPressed && mHover != null && mHover != mMouse[0].current)

UICamera.cs line 738

1. if (!isPressed && mHover != mMouse[0].current)

to

1. if (useMouse && !isPressed && mHover != mMouse[0].current)

[loopyllama]

I started a reply about how that isn't quite correct, then I dug a little deeper and you are right.
NGUI uses ProcessMouse() to handle "touches" while in the editor, but it still sends out OnHover in ProcessMouse() unless you change the lines you mention.

This means if you have only useTouch checked, in the editor you will get OnHover messages that you will never get on a mobile device.
Nice catch.

[ArenMook]

Ok, I've made the change on my end as well. Thanks!

[seandanger]

In a related note, would you agree that a gameObject should receive the OnHover(false) event even when moving out of the collider with the mouse pressed down?  I'd like my buttons to behave that way, and in order to do so, I have to remove the !isPressed check.  Here's what my line looks like:

1. if (useMouse && mHover != null && mHover != mMouse[0].current)

This functions as I would expect. 

If this change is incorrect and the hover behavior is as-designed, how should I register to be notified in script that the mouse button is down but the cursor is no longer above the collider?  I'm writing a tool that I intend to distribute with NGUI free and I want this behavior to work for people without forcing each user to hand edit NGUI's camera code.

Thanks!

[ArenMook]

You can always keep an eye on UICamera.currentTouch and its hovered object to see what's under the touch. The code you've mentioned is highly likely to interfere with how the current event system functions, in particular with how button highlighting works. It's cleaner to handle via your drag script instead.

[Belfort]

Hi,

I have the 2.0.7c free version of NGUI and there is still that problem (button has onHover behavior after click with useTouch only). Unfortunately I discovered my UICamera has only few lines of code (without functions mentioned above).

So how can I fix that?

[ArenMook]

You can't fix it in the free version. You need the full version for that, and it's already been fixed there.

[Belfort]

 

Why is that? Are there any additional shortage?
I thought:

"What's the catch? Aside from the non-commercial usage restrictions, NGUI's "Free Edition" message will be shown when you launch your application, and NGUI's watermark will appear in the top-left corner. Example 3 is also missing (orc inventory), because it's a bonus example."

I wanted to implement as much GUI as I can without any money spending, and buy full version of NGUI just before software realase. Is that possible?

[PhilipC]

For us to release NGUI Free we lock down a lot of the key code into the dll's. Doing this is a lot of work and sometimes issues arise which take even more time to solve. Because of this we don't release a new free version when we release the paid version. Currently the paid version is at 2.1.6 so the free version is roughly 10 version and 3 months behind.

Some other short comings from the free version are related to mobile devices. We have had reports that NGUI does receive input properly on mobile and possibly some other issues.