Mouse over with eye, change inv. descriptiosn

[Roja]

I was thinking, what if instead of clicking on each individual item with the eye icon when you want to see their descriptions in your Inventory Window, that when you simply move the mouse over with the eye icon that description changes?

 

Is this possible? Do you thinkit's a good idea? Remember it would only work in the inv. window with the eye icon.

[Learner]

I was thinking, what if instead of clicking on each individual item with the eye icon when you want to see their descriptions in your Inventory Window, that when you simply move the mouse over with the eye icon that description changes?

 

Is this possible? Do you thinkit's a good idea? Remember it would only work in the inv. window with the eye icon.

Since the icons aren't unique, the client doesn't know what description to show unless more information is provided by the server.

[Wytter]

Plus we would not be able to dynamically add new items (Unless an update mechanism is implemented, and this has some other issues).

[crusadingknight]

Plus we would not be able to dynamically add new items (Unless an update mechanism is implemented, and this has some other issues).

 

Well, if we had unique IDs, couldn't we cache the retrieved descriptions for the duration of the session?

Ie. Look cursor mouseover item->

If unique ID info cached--> Display cached info |

Else retrieve unique ID info from the server, cache for session (until client is shutdown).

 

Not that this would be a very clean, elegant, or nice solution.

[Roja]

Ok well it's not that important. I'm just looking for ways to reduce clicking, which can lead to health problems :/

[Placid]

Plus we would not be able to dynamically add new items (Unless an update mechanism is implemented, and this has some other issues).

 

Well, if we had unique IDs, couldn't we cache the retrieved descriptions for the duration of the session?

Ie. Look cursor mouseover item->

If unique ID info cached--> Display cached info |

Else retrieve unique ID info from the server, cache for session (until client is shutdown).

 

Not that this would be a very clean, elegant, or nice solution.

Why does it have to be cached for the session?

[crusadingknight]

Why does it have to be cached for the session?

 

Because it makes absolutely no sense to resend it every time, and because permanently saving info to the HD causes problems already discussed.

[Drakos7]

I would love to see unique IDs...