Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

userCalcs10 screen renders poorly in Phoebus #29

Closed
prjemian opened this issue Jan 2, 2024 · 5 comments · Fixed by #30
Closed

userCalcs10 screen renders poorly in Phoebus #29

prjemian opened this issue Jan 2, 2024 · 5 comments · Fixed by #30
Labels

Comments

@prjemian
Copy link
Contributor

prjemian commented Jan 2, 2024

Something is wrong with the handling of the box size for the 10 widgets:
image

Not a problem for other screens, such as userArrayCalcs10:
image

@prjemian prjemian added the bug label Jan 2, 2024
@prjemian prjemian changed the title userCalc10 screen renders poorly in Phoebus userCalcs10 screen renders poorly in Phoebus Jan 2, 2024
@prjemian prjemian transferred this issue from epics-modules/xxx Jan 3, 2024
@MarkRivers
Copy link
Member

The problem is that CSS is adding sliders, presumably because the widgets are larger than the allotted size in the display. This is a composite display using the userCalcs_line.bob for each row. I have played with both the CSS screens and the medm screens to try to fix the problem, but have not succeeded yet.

@prjemian
Copy link
Contributor Author

prjemian commented Jan 3, 2024

Odd that userTransforms10 does not have the same behavior. Uses similar design.

userCalcs_line box is 215x20

composite {
object {
x=0
y=120
width=215
height=20
}
"composite name"=""
"composite file"="userCalcs_line.adl;P=$(P),N=6"
}

display {
object {
x=1446
y=245
width=215
height=20
}
clr=64
bclr=3
cmap=""
gridSpacing=5
gridOn=0
snapToGrid=0
}

userTransforms_line box is 195x20

composite {
object {
x=0
y=120
width=195
height=20
}
"composite name"=""
"composite file"="userTransforms_line.adl;P=$(P),N=6"
}

display {
object {
x=1685
y=176
width=195
height=20
}
clr=64
bclr=3
cmap=""
gridSpacing=5
gridOn=0
snapToGrid=0
}

@prjemian
Copy link
Contributor Author

prjemian commented Jan 3, 2024

Looking at a difference between adl/userCalcs_line.adl and bob/userTransforms_line.bob, the Calcs screen has text widgets for ON and PUT that are not in the Transforms screen. The .bob file says:

yet the phoebus editor shows the height has increased by 1:

image

@prjemian
Copy link
Contributor Author

prjemian commented Jan 3, 2024

This line is important:

<auto_size>true</auto_size>

Changing it false keeps the widget from resizing the box but still the scroll bars are drawn. Dropping the font size and box vertical size to 9 for the two text widgets keeps the scroll bars from appearing in the phoebus display.

I suggest reducing the font size and vertical box size in the .adl file for the two text widgets. This will resolve the display problem in userCalcs10.bob and userCalcs20.bob.

@prjemian
Copy link
Contributor Author

prjemian commented Jan 3, 2024

Just the box height. MEDM sets the font size from the box height. Locally, with this change:

diff --git a/calcApp/op/adl/userCalcs_line.adl b/calcApp/op/adl/userCalcs_line.adl
index 65fd961..2341f9a 100644
--- a/calcApp/op/adl/userCalcs_line.adl
+++ b/calcApp/op/adl/userCalcs_line.adl
@@ -158,7 +158,7 @@ text {
                x=195
                y=10
                width=20
-               height=10
+               height=9
        }
        "basic attribute" {
                clr=14
@@ -174,7 +174,7 @@ text {
                x=195
                y=0
                width=20
-               height=10
+               height=9
        }
        "basic attribute" {
                clr=14

then convert to BOB:

phoebus.sh -main org.csstudio.display.converter.medm.Converter -output /tmp/ -force userCalcs_line.adl

the screen looks as expected in phoebus:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants