Using Arrow Keys to navigate Scroll View

[morgue]

Hi,

I'm trying to use arrow keys to navigate a scroll view, and it works fine, what I do is that I send a click message to the button on my left, or right, of whichever button I have currently selected, the issue is that when I use mouse scroll, and then the arrows, the button the arrows "choose" executes it's code, but the selection is left on the one the scroll chose.

I really can't tell what I'm missing. Any suggestions on how to achieve this?

Thanks.

[morgue]

Ok If I do something like:

1. UICamera.selectedObject = GameObject.Find("World 02");
2. print (UICamera.selectedObject.name);
3.  

it doesn't print world 02

it seems to give priority to the mouse

[ArenMook]

No idea what you meant by this:

the button the arrows "choose" executes it's code, but the selection is left on the one the scroll chose.

What version of NGUI are you using? If it's an older one then the selection change is a delayed process.

[morgue]

This would be the process with 2 buttons (A, and B).

Each have "print A or B" respectively.

A is selected.
Press right key on keyboard.
B is selected. Prints B.
Use mouse scroll to move to A.
A is now selected.
Press right key on keyboard.
A remains selected. But it Prints B.

I have a Game Object array with the buttons 'list' that checks the input, so if I'm on 0, right key is "cilck on 1", and so on.

Is there a way to know the exact NGUI version I'm on? I know I'm at least on 4.5.5.

[ArenMook]

4.5.5 is the version of Unity, not NGUI. The NGUI version is mentioned in the readme file.

You are talking about highlighting here. Mouse highlighting and keyboard highlighting are different for obvious reasons. Mouse is based on hover, keyboard is based on selection. You generally shouldn't be mixing 2 types of input here. Use either mouse or keyboard, not both. If you do use both, then yes you will have issues with highlighting.

[morgue]

Sorry about that. The readme says it's version 3.7.8, but the file is called ReadMe - 3.6.0.

I mean, some users could try to use both, which is why I wanted to handle it like this. I guess I can disable scrollwheel, but it would be nice to have it so it works either way.

[ArenMook]

I suggest updating the the latest as 3.7.8 is a few months out of date.