Skip to content

Make user record DESC field values consistent - #45

Merged
keenanlang merged 1 commit into
epics-modules:masterfrom
jlmuir:make-user-desc-consistent
Oct 1, 2026
Merged

keenanlang merged 1 commit into
epics-modules:masterfrom
jlmuir:make-user-desc-consistent

Conversation

@jlmuir

@jlmuir jlmuir commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

The DESC field values of some user records are not consistent with others. For example, one might have a space before the record instance number, while the rest do not. Or some might have a space after "user" when others do not. Or some might start with "User" when others start with "user".

Here are some examples of MEDM screens showing this:

MEDM-userArrayCalc MEDM-userCalcOut MEDM-userStringCalc MEDM-userStringSeq MEDM-userTransform

Make them all consistent.

The DESC field values of some user records are not consistent with
others.  For example, one might have a space before the record instance
number, while the rest do not.  Or some might have a space after "user"
when others do not.  Or some might start with "User" when others start
with "user".  Make them all consistent.
@MarkRivers

Copy link
Copy Markdown
Member

I think this PR is fine.

However, in practice it won't have much effect. The .DESC fields for all these records are the .req files, and hence in autosave. If users load these new .db files into an existing IOC they won't see the changes, because those values will be overridden by the autosaved values. Additionally the .DESC fields are really meant to be modified to give meaningful descriptions to the calculations, so the values in the .db files are often intentionally replaced and these new values are restored with autosave.

@jlmuir

jlmuir commented Sep 30, 2026

Copy link
Copy Markdown
Contributor Author

Agreed. I happened to add them to a new IOC and then saw this, so I thought I'd fix it. :-)

@keenanlang
keenanlang merged commit 59d1fe5 into epics-modules:master Oct 1, 2026
6 checks passed
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

Successfully merging this pull request may close these issues.

3 participants