Skip to content

Replace TextField by TextArea for PV list Name edition in app-alarm-ui and core-ui #2090

Closed

Description

@katysaintin

It will be more convenient to use a TextArea instead of TextField for listing the PV name to add in Alarm Service

Code to change :

  • app-alarm-ui org.phoebus.applications.alarm.ui.tree.AddComponentAction.java
    Line 45 replace private final TextField name = new TextField(); by private TextArea name = new TextArea();
  • core-ui : org.phoebus.ui.autocomplete.AutocompleteMenu.java
    Line 113 replace TextField by TextInputControl (TextInputControl is the mother-class of TextField and TextArea)

Activity

  1. georgweiss commented on Dec 17, 2021

    @georgweiss
    Collaborator

    Feel free to create a pull request that we can approve.

  2. katysaintin commented on Dec 17, 2021

    @katysaintin
    ContributorAuthor

    I try to commit my suggestion in my own branch CSSTUDIO-2090 but I'm not authorized. Do you know if I need specific credentials to contribute ? Thank you (I use my login katysaintin and my github password)

  3. kasemir commented on Dec 17, 2021

    @kasemir
    Collaborator

    I don't think there are any restrictions on using github to fork, commit to your fork, then create a PR

  4. kasemir commented on Jan 27, 2022

    @kasemir
    Collaborator

    Since this change, on our linux systems in the control room, we can no longer enter PV names.
    For" Type: Node" selected, you can enter text into the text area. For "Type: PV/s", pressing any key opens the PV name completion drop-down, and you can no longer enter anything.
    For other plain text fields like in Probe the PS name completion drop-down still allows editing the PV name, so the issue is somewhere in the text area and/or how the alarm's "Add .." dialog uses it.

  5. georgweiss commented on Jan 28, 2022

    @georgweiss
    Collaborator

    I'm seeing the same issue on MacOS. The problem occurs in AutoCompleteMenu L91 which assumes that the input component is a TextField. I changed the cast to TextInputControl, which fixes the issue.

    Will submit a PR once I have done some more testing.

  6. added a commit that references this issue on Jan 28, 2022
  7. katysaintin commented on Jan 28, 2022

    @katysaintin
    ContributorAuthor

    I'm seeing the same issue on MacOS. The problem occurs in AutoCompleteMenu L91 which assumes that the input component is a TextField. I changed the cast to TextInputControl, which fixes the issue.

    Will submit a PR once I have done some more testing.

    Yes you are right , I have miss this one. Thank you for your correction, tell me if you have no time to do it.

  8. georgweiss commented on Jan 28, 2022

    @georgweiss
    Collaborator

    Already done, pending in #2118

  9. added a commit that references this issue on Jan 28, 2022
  10. kasemir commented on Jan 28, 2022

    @kasemir
    Collaborator

    Thanks, that was quick!

  11. georgweiss commented on Jan 28, 2022

    @georgweiss
    Collaborator

    Well, I'm about to release a new version at ESS...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions