Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Container would not draw children when draw was called #125

Merged
merged 13 commits into from
Nov 10, 2024

Conversation

midwan
Copy link
Collaborator

@midwan midwan commented Nov 9, 2024

If we create a Container widget, and add some items to it (like an icon and a label in my example case), they never get drawn when the container's "draw" function is called.

To fix this, I'm adding a drawChildren function that will iterate through any child widgets and trigger the draw function on them.

Not sure if there's a better way around this, but this worked for me. :)

@midwan midwan requested a review from Jarod42 November 9, 2024 16:33
src/widgets/container.cpp Outdated Show resolved Hide resolved
@Jarod42 Jarod42 merged commit e0a581b into master Nov 10, 2024
6 checks passed
@midwan midwan deleted the container-drawchildren branch November 10, 2024 18:01
midwan added a commit to midwan/guisan that referenced this pull request Nov 13, 2024
commit 85989b7
Author: Jarod42 <Jarod42@users.noreply.github.com>
Date:   Mon Nov 11 10:07:54 2024 +0100

    [cleanup] Fix some MSVC warnings
    - C4127 conditional expression is constant
    - C4189 '%var': local variable is initialized but not referenced

commit e0a581b
Author: Dimitris Panokostas <midwan@gmail.com>
Date:   Sun Nov 10 17:49:04 2024 +0100

    Fixed Container would not draw children when draw was called (kallisti5#125)

    * Use const in more places

    * Revert "Use const in more places"

    This reverts commit 125b4aa.

    * Fixed container would not draw child objects when draw was called on it

    If we had a container with child objects, they would not be updated/drawn when the container's "draw" function was called.

    * Use for range loop, fix compiler warnings

    - Use for range loop
    - Fix warnings about type mismatch (int vs unsigned int)

    * Use =0 for new functions, use default for destructor

    * Revert "Use =0 for new functions, use default for destructor"

    This reverts commit 468fc20.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants