[http://sourceforge.net/p/ufoai/bugs/2258 Item 2258] imported from sourceforge.net tracker on 2013-01-28 19:26:38

tested in r27771
the scroll wheel does not affect certain grids when the checkbox is a control in the grid.
For example, you cannot mouse wheel scroll the hire employee screen when the mouse is hovering on or between or near the checkboxes in the grid.
Another example is in the aircraft screen, where you associate troops or pilots to the aircraft.
The attached screen shot shows the area that is and is not affected by the mouse scroll wheel. I am expecting that the mouse scroll wheel work whenever its in the datagrid area.
===== Comments Ported from Sourceforge =====

====== markhawrylak (2010-01-03 07:20:54) ======

areas of screen where scroll wheel does not work
====== tlh2000 (2010-01-03 09:19:32) ======

i suppose this is because the checkbox has the focus - maybe a node should be skipped if no action for the hit key (in this case the mouse wheel) is defined, bayo - would that easily be possible?
====== bayo-fr (2010-01-07 23:17:58) ======

What's the current way to code that:
* We must define wheel up/down every where it is need, this zone and all checkbox should define this events to scroll the scrollbar

What we should have:
* When wheel event is not defined on the node, we should call the parent event, if no wheel event on the parent, we should call the parent of the parent event...
That's on my todo list.
====== tlh2000 (2010-01-24 13:48:18) ======

nice it's already on your todo - will this be fixed for 2.3? or should we postpone it?
====== bayo-fr (2010-01-24 14:05:56) ======

It is not hard to do, but every time we change global behaviour like that we can create strange things.

Then, should we do it for 2.3? Maybe it is not very dangerous, but i ask.
====== tlh2000 (2010-02-03 07:37:00) ======

depends on what must be done for this - if it's something very major, we should postpone it to later versions imo. if it's only a few changes that don't have an impact on every other existing node in the scripts, we should do it. it it's hard to say and needs retesting for every single menu node - postpone.