Change Details

This is partly a fix of rP25077 & partly a fix of rP3802 Using down/up to change the map in the map selection dropdown in the gamesetup has a one-element lag. The reason is that on dropdown up/down, two events are sent: - first the current selected item is re-set. - then the new item is selected. Because of faulty timer logic, only the first update went through. Why the C++ code did this though, I cannot say. Removing it seems to work just fine.

This is partly a fix of rP25077 & partly a fix of rP3802 Using down/up to change the map in the map selection dropdown in the gamesetup has a one-element lag. The reason is that on dropdown up/down, two events are sent: - first the current selected item is re-set. - then the new item is selected. Because of faulty timer logic, only the first update went through. ~~Why the C++ code did this though, I cannot say. Removing it seems to work just fine.~~ This 'anchored' the up/down movement to the hovered element. Page up/page down changed the selection then, for some reason.

This is partly a fix of rP25077 & partly a fix of rP3802 Using down/up to change the map in the map selection dropdown in the gamesetup has a one-element lag. The reason is that on dropdown up/down, two events are sent: - first the current selected item is re-set. - then the new item is selected. Because of faulty timer logic, only the first update went through. ~~Why the C++ code did this though, I cannot say. Removing it seems to work just fine.~~ This 'anchored' the up/down movement to the hovered element. Page up/page down changed the selection then, Removing it seems to work just finefor some reason.