Skip to content

Class hierarchy is a bit messy for few visualization pipelines #207

Description

@mxochicale

For the record, the following list of classes inherent Qt objects that might create issues with data pipelines (e.g. #202), also I don't see any logic in the class hierarchy but different users prototyping their own pipelines.

class VTKOverlayWindow(QVTKRenderWindowInteractor)
class VTKRenderingGenerator(QtWidgets.QWidget)
class VTKStereoInterlacedWindow(QtWidgets.QWidget)
class VTKLUSSimulator(rg.VTKRenderingGenerator)

Hence, if we would like to fix the above, I would suggest the following steps:

Metadata

Metadata

Assignees

No one assigned

    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