I believe all of the synApps screens have text-entry widgets for both the INPx and x value fields.
I checked the auto settings .req files and they save both the INPx and x value fields in autosave.
Changing the behavior so constant link fields cannot be changed at run-time should thus not break existing databases, since the x value fields will be autorestored. It would require training users to enter new constants into the value fields, not INP fields.
Mark
-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Andrew Johnson via Core-talk
Sent: Tuesday, April 23, 2019 10:57 AM
To: Andrew Johnson <email address hidden>
Subject: Re: [Merge] ~anj/epics-base/+git/base-7.0:fix-1824277 into epics-base:7.0
Hi Keenan,
Does synApps have GUI screens that have a text-entry widget for the INP fields but only a text-display widget for the corresponding value field on these record types? That's the other case I'm most concerned about.
- Andrew
On 4/23/19 10:41 AM, Lang, Keenan C. wrote:
>From a scan of our IOC's, it crops up in user calcs, pid calculations and limits, slit transforms, bpm calculations, cmdReply formatting, shutter arming, and a database for fastshutter limits.
________________________________
From: Mooney, Tim M.
Sent: Tuesday, April 23, 2019 10:11:53 AM
To: Johnson, Andrew N.; <email address hidden><mailto:<email address hidden>>; Lang, Keenan C.; <email address hidden><mailto:<email address hidden>>
Subject: Re: [Merge] ~anj/epics-base/+git/base-7.0:fix-1824277 into epics-base:7.0
>>What is the bug?
>Record types that are based off of calcout can no longer have a constant value written to their input fields and have the >value of the correct data field change. For example, writing '5' to a calcout's INPA field no longer changes the A field to >5. This affects the calcout, aCalcout, sCalcout, transform, and luascript records.
I'm sure I've never written a database that relies on this behavior.
Tim Mooney (<email address hidden><mailto:<email address hidden>>) (630)252-5417 Beamline Controls Group (www.aps.anl.gov<http://www.aps.anl.gov>)
Advanced Photon Source, Argonne National Lab
________________________________
From: <email address hidden><mailto:<email address hidden>> <email address hidden><mailto:<email address hidden>> on behalf of Keenan Lang via Core-talk <email address hidden><mailto:<email address hidden>>
Sent: Tuesday, April 23, 2019 9:43 AM
To: Johnson, Andrew N.
Subject: Re: [Merge] ~anj/epics-base/+git/base-7.0:fix-1824277 into epics-base:7.0
I don't think this release will officially support EPICS 7, but I am definitely going to try to start getting all of our code compliant with newer versions. That's what ended up finding this issue as I was updating some of my own code for the changes to links.
>I understand this seems like a rush, but a synApps release strikes me as a good reason to try and get this fix included.
Since the whole of synApps isn't likely to use EPICSv7 at least for the next year or more, there's not really a rush. The only IOC's going in that use it will be for specific areaDetector cameras and they don't really use the record types affected.
>What is the bug?
Record types that are based off of calcout can no longer have a constant value written to their input fields and have the value of the correct data field change. For example, writing '5' to a calcout's INPA field no longer changes the A field to 5. This affects the calcout, aCalcout, sCalcout, transform, and luascript records.
-- https://code.launchpad.net/~anj/epics-base/+git/base-7.0/+merge/366247
Your team EPICS Core Developers is requested to review the proposed merge of ~anj/epics-base/+git/base-7.0:fix-1824277 into epics-base:7.0.
--
Arguing for surveillance because you have nothing to hide is no different than making the claim, "I don't care about freedom of speech because I have nothing to say." -- Edward Snowdon
I believe all of the synApps screens have text-entry widgets for both the INPx and x value fields.
I checked the auto settings .req files and they save both the INPx and x value fields in autosave.
Changing the behavior so constant link fields cannot be changed at run-time should thus not break existing databases, since the x value fields will be autorestored. It would require training users to enter new constants into the value fields, not INP fields.
Mark
-----Original Message----- base/+git/ base-7. 0:fix-1824277 into epics-base:7.0
From: <email address hidden> <email address hidden> On Behalf Of Andrew Johnson via Core-talk
Sent: Tuesday, April 23, 2019 10:57 AM
To: Andrew Johnson <email address hidden>
Subject: Re: [Merge] ~anj/epics-
Hi Keenan,
Does synApps have GUI screens that have a text-entry widget for the INP fields but only a text-display widget for the corresponding value field on these record types? That's the other case I'm most concerned about.
- Andrew
On 4/23/19 10:41 AM, Lang, Keenan C. wrote:
>From a scan of our IOC's, it crops up in user calcs, pid calculations and limits, slit transforms, bpm calculations, cmdReply formatting, shutter arming, and a database for fastshutter limits.
_______ _______ _______ _______ ____ <mailto: <email address hidden>>; Lang, Keenan C.; <email address hidden> <mailto: <email address hidden>> base/+git/ base-7. 0:fix-1824277 into epics-base:7.0
From: Mooney, Tim M.
Sent: Tuesday, April 23, 2019 10:11:53 AM
To: Johnson, Andrew N.; <email address hidden>
Subject: Re: [Merge] ~anj/epics-
>>What is the bug?
>Record types that are based off of calcout can no longer have a constant value written to their input fields and have the >value of the correct data field change. For example, writing '5' to a calcout's INPA field no longer changes the A field to >5. This affects the calcout, aCalcout, sCalcout, transform, and luascript records.
I'm sure I've never written a database that relies on this behavior.
Tim Mooney (<email address hidden> <mailto: <email address hidden>>) (630)252-5417 Beamline Controls Group (www.aps.anl.gov<http:// www.aps. anl.gov>)
Advanced Photon Source, Argonne National Lab
_______ _______ _______ _______ ____ <mailto: <email address hidden>> <email address hidden> <mailto: <email address hidden>> on behalf of Keenan Lang via Core-talk <email address hidden> <mailto: <email address hidden>> base/+git/ base-7. 0:fix-1824277 into epics-base:7.0
From: <email address hidden>
Sent: Tuesday, April 23, 2019 9:43 AM
To: Johnson, Andrew N.
Subject: Re: [Merge] ~anj/epics-
>Keenan Lang is working to release synApps 6.1 by the end of May (see /github. com/epics- modules/ iocStats/ issues/ 33#issuecomment -484995
>his question at
>https:/
>327), but I don't know if that is intended to support EPICS 7
I don't think this release will officially support EPICS 7, but I am definitely going to try to start getting all of our code compliant with newer versions. That's what ended up finding this issue as I was updating some of my own code for the changes to links.
>I understand this seems like a rush, but a synApps release strikes me as a good reason to try and get this fix included.
Since the whole of synApps isn't likely to use EPICSv7 at least for the next year or more, there's not really a rush. The only IOC's going in that use it will be for specific areaDetector cameras and they don't really use the record types affected.
>What is the bug?
Record types that are based off of calcout can no longer have a constant value written to their input fields and have the value of the correct data field change. For example, writing '5' to a calcout's INPA field no longer changes the A field to 5. This affects the calcout, aCalcout, sCalcout, transform, and luascript records. /code.launchpad .net/~anj/ epics-base/ +git/base- 7.0/+merge/ 366247 base/+git/ base-7. 0:fix-1824277 into epics-base:7.0.
--
https:/
Your team EPICS Core Developers is requested to review the proposed merge of ~anj/epics-
--
Arguing for surveillance because you have nothing to hide is no different than making the claim, "I don't care about freedom of speech because I have nothing to say." -- Edward Snowdon
-- /code.launchpad .net/~anj/ epics-base/ +git/base- 7.0/+merge/ 366247 base/+git/ base-7. 0:fix-1824277 into epics-base:7.0.
https:/
Your team EPICS Core Developers is requested to review the proposed merge of ~anj/epics-