Ticket #10445 (new)
InstrumentWindow should have a refresh/update method to change the instrument
Reported by: | Federico M Pouzols | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Backlog |
Component: | GUI | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description (last modified by Federico M Pouzols) (diff)
This method would make it possible to update the instrument window with a different workspace/underlying data.
The idea is that if one is using a single instrument window instance, it should not be necessary to close it and open a new one to visualize a different instrument.
This is related to/motivated by ticket #8091.
Destroying an instrument window and creating a new one does not seem to take a significant amount of time, at least in the few tests that I did. So I'd say that ticket has a low benefit/effort ratio and consequently low priority, as it may require careful testing of proper initialization, etc.
Change History
Note: See
TracTickets for help on using
tickets.