Incorrect behaviour of the popup list

[DFTGames]

Hi,

I'm delivering an app that uses database originated data to make selections. During last test my client added a lot of options in the DB and... we found out that the popup list goes off screen 

Before I start hacking the code I wanted to know if there is any plan to fix this, containing the popup list within the screen and showing a scroll bar when needed.

Thanks for this great tool!
Pino

[ArenMook]

There is currently no plans to change this. As I always mention, long popup list is a design issue. No one likes scrolling through items to select one of them. Try breaking it up into several lists instead, or use a grid-based selection widget instead, like I do for the sprite selection in NGUI.

[DFTGames]

Hi,

not really a design problem, the data can't be split, it's just like the US state selection (those will go off screen as well), and the client wants it in a popup list, so from a design point of view there is no error and no issue, it has to be that way because it's correct, it makes no sense to split them up and on a grid based widget it looks ugly 

Time to hack the code then... 

[ArenMook]

Instead of using a popup list, have it be a button that brings up a clipped panel with a scrollable list inside.

[SkobbejakGames]

The problem is what about stuff like resolution lists, these need to be detected based on the players specs and screen, and some people have multiple screens which can cause a bunch of resolutions to be added to the array. The thing is generating this list in run time in a scroll menu would be an extrem pain compared to a popup list and these resolutions cant be split up theyt do all need to be in the same pop up list.

I really dont get the design problem argument. Its the same difference weither its a "popup list" with a "scrollbar" included VS a "scroll menu". The main difference being the popup list is a lot easier to generate its array list during runtime, where this is a bit more complicated and tedious with a scroll menu.

If other people have already added this themselves then it shouldnt be too difficult to do either, the problem with using their solutions is that you would need to re-inlcude those changes with each update of NGUI and if the internals change those custom fixes are useless then and need to be overhauled as well.