Closed soc-pe-bot closed 5 days ago
That's a good observation! However, based on our implementation, this is indeed the correct behaviour of MainWindow. In our actual implementation, the MainWindow class still holds a reference to exactly one ClientListPanel, MeetingListPanel and PropertyListPanel each throughout its lifecycle regardless of which panel is being displayed (i.e. the panels that aren't being displayed are just not being displayed, but a reference to them are still kept to them within the respective fields of the MainWindow class, which aligns with the definition of association and multiplicity of one. Hope that clears that up!
Detail:
The multiplicity should be optional (0..1) for ClientListPanel, MeetingListPanel, and PropertyListPanel as only one panel is being displayed at a time.
Screenshot:
Labels:
type.DocumentationBug
severity.VeryLow
original: hweinian/ped#13