#24 closed defect (fixed)
Clean up the signals and slots
| Reported by: | diane | Owned by: | diane |
|---|---|---|---|
| Priority: | minor | Milestone: | Few Small Repairs |
| Component: | Qt Gui | Version: | |
| Keywords: | Cc: |
Description
I don't think I've set up the signals & slots for updating the various dynamic bits of my app all that well. Especially with respect to the components handling the PathWidget.
That whole hierarchy needs to be refactored.
Change History (3)
comment:1 by , 19 years ago
| Status: | new → assigned |
|---|
comment:2 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 18 years ago
| Summary: | Clean up the signals & slots → Clean up the signals and slots |
|---|---|
| Type: | → defect |
| Version: | 2.0 |
Note:
See TracTickets
for help on using tickets.
It could've been more refactored, but the API is fairly straightforward and i'm not going to bother. (The following comment came from SequenceBrowserWidget.cpp about what more could be done.
This could theoretically be pushed down to some set of signals and slots connecting SequenceDescriptions and some signal emitted by the browser's viewportChanged code but evertime I tried to figure it out, I got confused about how the descriptions in one of the sidebars was supposed to know if it was mapping the rightbase or the leftbase. And so though this could be better the typical use cases can just talk to the SequenceBrowserWidget for rendering or mussa output.