Please help to review the PR:
https://github.com/lsst-ts/ts_m2gui/pull/11

Thanks!

A general comment: I see that you need to create a diagnostics tab scrollable to fit on a smaller screen. While this might work, this will not work if you still want to see diagnostics on a small screen.

What you can do instead of scrolling is you can put the Digital Inputs and Digital Outputs indicator into your own widget. That will be shown either from the main menu (combo box), or when the user clicks a button in the diagnostics tab (which itself can be colored to see if there are any problems with output/input). I will append screencast showing how LBT GUI handles this, or see how I show details of errors in M1M3GUI.

Right now, I tried to make the Python EUI to look like the LabVIEW EUI as much as possible (the users are used to the LabVIEW EUI for some time already). After I replaced the LabVIEW EUI with Python EUI on summit, I would do your suggestion at that time. I tried to keep the similar user experience at each version update (like the Mac instead of Windows). Thanks!

As a reference, this is what LabVIEW has at this moment:

Thanks for the review in the GitHub and provide many precious suggestion that I could use in the future's refactoring.