#14906 closed enhancement (wontfix)
RFE: Start core tools before initializing bundles
Reported by: | Zach Pearson | Owned by: | Zach Pearson |
---|---|---|---|
Priority: | moderate | Milestone: | |
Component: | UI | Version: | |
Keywords: | Cc: | chimerax-programmers | |
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
By 'core tools' I mean the toolbar, rapid access menu, log, model menu, command line, and status line. By getting GUI or NoGui or headless initialization out of the way before running other bundles' initializers, we could have bundles like medical_imaging that e.g. reconfigure the toolbar.
Change History (3)
comment:1 by , 19 months ago
Cc: | added; removed |
---|
comment:2 by , 19 months ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
That's a much better idea!
comment:3 by , 19 months ago
Alternatively, you could register for the chimerax.core.tools.ADD_TOOL_INSTANCE trigger, like you already do in your segmentations module to modify the Volume Viewer tool.
Note:
See TracTickets
for help on using tickets.
I don't know if you mean just custom initializations or also manager/provider initializations. I can't really adequately describe how many pitfalls I foresee with this approach. I think the right approach here would be for the medical-imaging bundle, in its custom initialization, to register for the session.ui.triggers' "ready" trigger (if session.is_gui), which fires once the main GUI is initialized, including starting any auto-started tools (which typically includes the toolbar).