Skip to content

QML component caching gets in the way of easy updating components #4

Description

@bwachter

We don't explicitely destroy components, but expect that the after stackview.pop no references exist, and they then get garbage collected, so the next instance has to be loaded from file again. This doesn't really work, so we probably need to have a mix of explicitely destroying components, and kicking the garbage collector/cleaning the cache.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions