I’m seeing my ScrollBar::Listener::scrollBarMoved() sometimes reporting an outdated start position - the previous one. I didn’t dive into the compiled code, but without memory fences, it seems possible for the async notification made from within setCurrentRange[Start] to occur before the actual update, which would explain my results.
Before diving further into this, I wanted to ask whether this is a known issue, or if anyone else has seen this behavior, or if there’s a guess that I’m doing something wrong (I’m just listening to notifications resulting from dragging/clicking the mouse on the scroll bar. I’m not doing any manual calls to the scrollbar to change the position).
Thanks,
Dan