Skip to content

Show active config path in window title#125

Open
ispielma wants to merge 1 commit into
labscript-suite:masterfrom
ispielma:UpdatedTitleBars
Open

Show active config path in window title#125
ispielma wants to merge 1 commit into
labscript-suite:masterfrom
ispielma:UpdatedTitleBars

Conversation

@ispielma

@ispielma ispielma commented Apr 7, 2026

Copy link
Copy Markdown

change the title bar of the main window of all labscript apps to read "app name - path to app_config_file" for example "runmanager - ~/labscript-suite/app_saved_configs/example_apparatus/runmanager/runmanager.ini".

This is helpful in verifying that the app is actually accessing the desired configuration file, which has been an ofttimes issue locally.

@dihm

dihm commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Could you help me understand the motivation behind this one a little better? I'm hesitant to add that much cruft to the title bars of all the apps for something that feels like a niche problem that has other potential solutions that aren't so top level.

It does appear that File-->Save configuration already lists the path for the currently loaded config file. Is it inaccurate in niche situations? If so, I'd just as soon fix that. I get that it is an extra click, but is this information that is really needed at a glance?

@ispielma

ispielma commented Jun 8, 2026

Copy link
Copy Markdown
Author

I guess first with a bit of rebuttal: most software indicates "the active file" (whatever than means) in the title bar, so I don't think that this should be considered as cruff.

The more substantive response is that, yes this currently appears in the File-->Save configuration menu dropdown, but this is very much not OS standard (so should be removed, ideally), so I think that violating OS GUI standards is a worse sin than updating the menu bar into a more standard form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants