mirror of
https://github.com/ultimatepp/ultimatepp.git
synced 2026-05-15 14:16:07 -06:00
[GH-ISSUE #273] Mouse events are ignored in LabelBox #85
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/ultimatepp#85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ortman on GitHub (Jun 1, 2025).
Original GitHub issue: https://github.com/ultimatepp/ultimatepp/issues/273
LabelBox is a container, if you add other controls to it, they will not respond to mouse events.
Example:
The button is not clicked by the mouse, because LabelBox is inherited from StaticText, in the constructor of which there is "IgnoreMouse();"
Solution:
Add to the constructor of the LabelBox class
NoIgnoreMouse();Do you support my proposal?
@mirek-fidler commented on GitHub (Jun 1, 2025):
LabelBox is not a container, just decoration.
(we are not going that direction. We want layout files, which is in direct
opposition to LabelBox being a container).
Mirek
On Sun, Jun 1, 2025 at 11:19 AM Sergey Ortman @.***>
wrote:
@ortman commented on GitHub (Jun 1, 2025):
Visually, it groups UI components.

Here is an example of a program, inside LabelBox I added my class with a layout. When resizing Labelbox, the class placed inside is stretched proportionally. It works and is convenient.
But the buttons are not pressed, because IgnoreMouse() is set;
@mirek-fidler commented on GitHub (Jun 1, 2025):
The problem is that if it would not ignore mouse, it would mess up with
usuall use in layouts where inside are its sibling widgets, by consuming
theirs mouse events.
Your usage is fine, but you can either make those child layouts sublings or
just call NoIgnoreMouse for your labelboxes. No need to completely nuke
current codebase....
On Sun, Jun 1, 2025, 12:24 PM Sergey Ortman @.***>
wrote:
@ortman commented on GitHub (Jun 1, 2025):
Now I understand why this default property cannot be changed. Thank you very much for the explanation.