# GUI ## Launch In `prod`: `ssh sls-vserv-bd-hla01` ``` cd /sls/bd/hla/prod/qt ../bin/sls_hla_launch_gui.sh A_BD_ServiceManager.ui ``` In `dev`: `ssh sls-vserv-bd-hla01-dev` ``` cd /sls/bd/hla/dev/qt ../bin/sls_hla_launch_gui.sh A_BD_ServiceManager.ui "dev" ``` Any extra arguments are passed straight through to `caqtdm`, e.g. to set a macro: ``` ../bin/sls_hla_launch_gui.sh A_BD_ServiceManager.ui "dev" -macro "OTHER_ENV_VAR=HEYHEY" ``` **Note:** launching straight from a git checkout, as above, uses the raw `.ui` files as committed - including the literal `{{ agebd_env_suffix_upper }}`/`{{ agebd_env_suffix_lower }}` placeholders in their PV names. Those only get substituted with `-DEV`/`-dev` (or emptied out, in `prod`) at deploy time, by `.gitea/workflows/deploy.yml`'s `"Qt - deploy"` step, on the *deployed* copy at `/sls/bd/hla//qt/`. If widgets show up blank or unresponsive, check whether you're accidentally pointing at the raw checkout instead of the deployed `.ui` file.