-
Notifications
You must be signed in to change notification settings - Fork 116
Fix issue in app-pvtable for PV that contains dot in the name the last part of the name is removed #3228
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
Merged
Merged
Fix issue in app-pvtable for PV that contains dot in the name the last part of the name is removed #3228
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
02250d9
Upgrade Maven plugin version to 3.6.3 for
katysaintin f7416b2
Revert "Upgrade Maven plugin version to 3.6.3 for git-commit-id-maven…
katysaintin 9721669
Update Maven version for git-commit compatibility
katysaintin 279cbf0
Comment git-commit-id-maven-plugin for jitpack
katysaintin 50b2fb7
Merge branch 'ControlSystemStudio:master' into master
katysaintin f42ada4
Merge branch 'ControlSystemStudio:master' into master
katysaintin 59b4d77
Merge branch 'master' of https://github.com/katysaintin/phoebus.git
katysaintin 7317c47
Fix bug for Variable that contains dot in the name and add a tooltip on
katysaintin 1e0b79c
Rebase on last master version
katysaintin 0a7c78a
Set maven version for jitpack build
katysaintin 85ce312
Specify maven version for jitpack
katysaintin 2df512a
Get the description from VType first or PV using DisplayProvider
katysaintin 7276f94
Merge branch 'ControlSystemStudio:master' into master
katysaintin 3f623d0
Merge branch 'ControlSystemStudio:master' into master
katysaintin c3ab02a
Add comment to explain why check if PV instanceof DisplayProvider see
katysaintin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 change: 1 addition & 0 deletions
1
app/pvtable/src/main/resources/org/phoebus/applications/pvtable/ui/messages.properties
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 change: 1 addition & 0 deletions
1
app/pvtable/src/main/resources/org/phoebus/applications/pvtable/ui/messages_fr.properties
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| before_install: | ||
| # update maven version 3.9.9 | ||
| - sdk install maven 3.9.9 | ||
| install: | ||
| - mvn install -DskipTests |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure how this will work. A value (VType) can be a DisplayProvider. A PV will never be a DisplayProvider.
The following check of
currentValue instanceof DisplayProvidermakes sense, butthePV instanceof DisplayProvidershould be removedUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please , it is the only way I found to manage EnumVType for Boolean value for my own datasource Muscade. VEnum and VBoolean Type are not implemented DisplayProvider , and the description is only defined for VNumber .. while a DESC field is a common field for EPICS, so I don't know how to consider the description for bo or bi ?
MuscadePV implements DisplayProvider , and it's simplify the code, avoiding test such as if datasource type is equals "ca" or not equals "sim" "loc" ...
The other point is, that create a DESC PV is complexify a lot , the code of the custom source.
Have you got a suggestion for me to solve my problem. Furthermore this test is not impacting the functionnement.
Thank you for the suggestion, else could I approve my pull request ?
Thank you for your understanding.
Katy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shroffk: Looks like the description was added to the wrong part of the VType and/or EPICS normative types.
DisplayProviderstarted out with units and the min/max values for display, control, alarms. Those only apply to numeric data, not strings, enumerated, booleans. Then the description was added because PVAccess happens to provide it, but you're correct, in principle there's a description for bool/enum/string, not just numerics.Alright, the PV Table cannot fix what's broken in channel access/pv access/normative types/vtypes. Still, maybe add a comment to the
thePV instanceof DisplayProvider:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that this seems like something not handled well by VType... primarily cause the description is available differently in ca vs pva
What I think would be the best way to address this would be to remove the description from the display.
So, enums, bool, strings can implement just the
DescriptionProviderand not have to provide adisplaywhich makes no sense for these types.I am afraid how much impact such a change would have on our codeabse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, a
DescriptionProviderwould be a better approach.Agree that this would be a painful change that also extends into the normative types/PVAccess, because it has the same idea for "display" information.
Let's defer that by about 5 years.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @kasemir and @shroffk ,
I'm totally agree with you about DescriptionProvider interface addition in core-pva .
I think it is the proper way to solve my issue.
And I also agree with that the impact on epics vtype clients could be problematic.
Thank you for your help, I'm OK with the comment , for clarifying the situation.
@shroffk I will make a pull request on core-epics vtype submodule.
Have a good day and thank you again.
Katy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shroffk & @kasemir
I add the comment you ve ask in previous comment.
Is ok for you , in waiting for VType's modifiations ?
Thank you again for your help :)