Good point about the 'height' vs 'horizontal', though I think we're safe as we currently have only these methods that start with scrollbar and end in h():

$ git grep scrollbar | grep 'h('
Fl_Browser_.H:  int scrollbar_width() const {
Fl_Browser_.H:  void scrollbar_width(int width) {
Fl_Text_Display.H:  int scrollbar_width() const {
Fl_Text_Display.H:  void scrollbar_width(int width) {

But those methods are all deprecated in favor of scrollbar_size(), to universally apply to the "short dimension" for both horizontal and vertical scrollbars. So 'height' and 'width' terminology is generally avoided for scrollbars. (Which is why we don't have scrollbar_height() anywhere in the API)

So I think we might be OK with scrollbar_v()/_h(), or for the longer scrollbar_vert()/_horiz().

scrollbar_x(), scrollbar_y() which stands for "scrollbar in { x, y } direction", resp.

I'm thinking that'd be even more easily confused with the x() and y() positions, so -1 on that.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.