You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally you'd configure your toolbars to open pydm screens using the related display option, but at times as in #100 this hasn't worked so well so some of these are launched as shell commands.
For RIX, this unveiled another issue where opening the chemRIX vacuum screen opened the screen in a strange state. The screen would open and display ok, but whenever we tried to open any of the typhos subdisplays e.g. from the valve or gauge icons the screen would freeze and then crash.
We tried to investigate what was going on by e.g. setting redirectCommandOutput to true and by setting the log level to debug but this actually ended up causing the screen to freeze on launch altogether.
For this use case we realized that it worked find by switching back to the related display option but this seemed like bizarre behavior to me. It's not immediately clear if this is a lucid bug, an environment misconfiguration bug, a pydm bug, a typhos bug, or a pcdswidgets bug.
Configuration snippit that failed to produce a useful screen:
Normally you'd configure your toolbars to open pydm screens using the related display option, but at times as in #100 this hasn't worked so well so some of these are launched as shell commands.
For RIX, this unveiled another issue where opening the chemRIX vacuum screen opened the screen in a strange state. The screen would open and display ok, but whenever we tried to open any of the typhos subdisplays e.g. from the valve or gauge icons the screen would freeze and then crash.
We tried to investigate what was going on by e.g. setting redirectCommandOutput to true and by setting the log level to debug but this actually ended up causing the screen to freeze on launch altogether.
For this use case we realized that it worked find by switching back to the related display option but this seemed like bizarre behavior to me. It's not immediately clear if this is a lucid bug, an environment misconfiguration bug, a pydm bug, a typhos bug, or a pcdswidgets bug.
Configuration snippit that failed to produce a useful screen:
The text was updated successfully, but these errors were encountered: