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

Rendering of Annotation Content Field on DataBrowser "unparses" the PV's (trace) EGU unexpectedly #2731

Open
ambarb opened this issue Jan 9, 2025 · 6 comments

Comments

@ambarb
Copy link

ambarb commented Jan 9, 2025

Using cs-=studio version 4.6.1 on Red Hat Enterprise Linux release 8.10 (Ootpa)

I would expect Torr to be displayed at the end of line 2 for the black trace called XF:23ID1-VA{Dif-CCG:1}P-I

image
image

@ambarb ambarb changed the title Rendering of Annotation Content Field on DataBrowser "unparses" the PV's (trace) EGU Rendering of Annotation Content Field on DataBrowser "unparses" the PV's (trace) EGU unexpectedly Jan 9, 2025
@kasemir
Copy link
Contributor

kasemir commented Jan 9, 2025

Is this caused by having ..{..}.. braces in the PV name?

@ambarb
Copy link
Author

ambarb commented Jan 9, 2025

All PVs at NSLS-II have ..{..}... Since I am only a user of cs-studio and EPCIS, this isn't something that is easy for me to test.

This issue isn't critical to fix for me, but I do not know what other features may be impacted so I thought it is best to report it.

@kasemir
Copy link
Contributor

kasemir commented Jan 9, 2025

The formatting seems to work fine for us here where we don't have ..{..}.. in PV names, so I assume the problem is related to having them in there.

@kasemir
Copy link
Contributor

kasemir commented Jan 10, 2025

Well, I cannot reproduce. Created some PV with curly braces in the name, added an annotation with text at the end, and the value with units stays intact, not moving the units to the end

Screenshot 2025-01-10 at 11 17 32 AM

@kasemir
Copy link
Contributor

kasemir commented Jan 10, 2025

Thought that maybe a PV name with {Dif-CCG:1} where the {..:1} could be mistaken for a formatting option would make a difference, but still can't reproduce

@kasemir
Copy link
Contributor

kasemir commented Jan 10, 2025

Tried a dummy record with your exact example name, works fine:

record(calc, "XF:23ID1-VA{Dif-CCG:1}P-I")
{
  field(INPA, "XF:23ID1-VA{Dif-CCG:1}P-I")
  field(CALC, "A<10?A+1:0")
  field(EGU,  "units")
  field(SCAN, "1 second")
}

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

No branches or pull requests

2 participants