At the begin, I also found it strange, what you wanted to get. But we can express the intend in a more general/abstract way:
A collection of clickable elements that needs more space than it can occupy on the screen (and whose size can be changed dynamically at run time). In fact, we have lots of such cases in an application and several different ways to get the intended result.
What about your unanswered July-question, the GtkListBox probably offers what you wanted. The widget emits two different signals: if an element is selected and if an element is activated (= clicked; even if it was already selected).
A collection of clickable elements that needs more space than it can occupy on the screen (and whose size can be changed dynamically at run time). In fact, we have lots of such cases in an application and several different ways to get the intended result.
Thank you very much for this abstraction of the problem. Iād like to add it to my first post, but unfortunately I canāt edit it.
What about your unanswered July-question, the GtkListBox probably offers what you wanted.
Iām not really sure which question youāre referring to, but as for this problem, GtkListBox did not help orIām using it wrong - I couldnāt get it to scroll automatically so I still had to put it inside a ScrolledWindow, whicht triggers the problematic behavior again.