What's up, RMers?

[DerVVulfman]

  I have a dedicated class for all graphics. And the buttons for the new scrolling listbox does not use what I used in the previous scrollbar.  So I either migrate these new buttons to that class, or see how to adapt the old ones to work.

DONE!    The only arrow buttons that don't share the same code are the resizable buttons for the numberbox widget as they stretch... not fixed to a 16x16 image.  And bonus, you can use the predefined render option or import a set of 16x16 arrows of your own.  Only the TAB indicator and numberbox arrows remain in-system rendered as they must scale to fit the widget/scrollbars.

  And I need to ensure that clicking on the scrollbar doesn't interfere with any currently highlighted/selected data.

Oh, that is SO done.

And when I  (1) change the size of the font, (2) add/remove items from the list or (3) change the height of the list, the scroll bar's increment system needs to be recalculated.

Scrolling does work.  But the tab indicator which you would normally be able to move up and down doesn't yet calibrate when you resize the window or add/remove content.  I would figure that would be the next update, and I assume should be the last insofar as the basic listbox widget itself is concerned.

That is now COMPLETELY fixed.  Scrolling the list and dragging the tab indicator up and down is smooth.

Of course, the number of items listed and the size of the initial window must be accounted for.
   Imagine having a list to 200 items but a window that only shows two at a time!  That'd be a mess.

My work on a scrolling listbox will become the replacement for my initial listbox widget.  It now 'auto-detects' when it needs to scroll or NOT to scroll.  With a noted exception that the window height MUST be at least a certain size lest the scrollbar won't fit.

True that!  And now, my scrolling listbox IS the replacement.   Operating perfectly, I replaced all my initial Listbox commands in the demo with the new one.

  But with what I have accomplished, replacing the combobox (or dropdown list box) may be readily be made in much the same fashion.

And that...     will be NEXT!