Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-391

Discuss Default Values for Graph Track Operations

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      While testing graph track operations from the track context menu I noticed that many of the mathematical operations give the user two options: "Default" or "Configure...".

      Selecting the "Default" option seemed to only copy the graph for the "Add" and "Subtract" operations and it reduced the values to "0" for the "Divide" and "Multiply" operations. This led me to suspect that the default value that was being applied to these operations was "0" and after checking with David it turns out that this is, in fact, the case.

      I believe that the default values for track operations should be discussed or whether or not the default option should even be selectable.

      When a user wants to apply a mathematical function to a graph track I don't think they would want to perform the function using a "hidden" default value, and certainly not by a value of "0".

      I think the best option would be to remove the "Default" AND "Configure" option from the track operations context menus and upon selecting a mathematical operation the "Configure" box would automatically appear.

      This is basically how the graph track operations work from the "Annotations tab" (forces the user to input a value) so it would be nice to be able to follow our own convention and remove user confusion with this story.

        Attachments

          Activity

          Hide
          tmall Tarun Mall (Inactive) added a comment -

          commit fe97313da4ed31814b8dff499e14a4eacdf4493c
          Author: Tarun K. Mall <c2tarun@hotmail.com>
          Date: Fri Apr 3 17:07:42 2015 -0400

          Remove default option from track operations.

          Show
          tmall Tarun Mall (Inactive) added a comment - commit fe97313da4ed31814b8dff499e14a4eacdf4493c Author: Tarun K. Mall <c2tarun@hotmail.com> Date: Fri Apr 3 17:07:42 2015 -0400 Remove default option from track operations.
          Hide
          mason Mason Meyer (Inactive) added a comment -

          It seems that there is a problem relating to mismatch and mismatch pileup graphs...the track operations section of the context menu is enabled but I can't make the drop-down menu appear. This is not happening in the Live Version so it must be related to recent changes.

          Ask Mason if clarification is needed. I am reassigning to Tarun and moving back into To-Do for changes.

          Show
          mason Mason Meyer (Inactive) added a comment - It seems that there is a problem relating to mismatch and mismatch pileup graphs...the track operations section of the context menu is enabled but I can't make the drop-down menu appear. This is not happening in the Live Version so it must be related to recent changes. Ask Mason if clarification is needed. I am reassigning to Tarun and moving back into To-Do for changes.
          Hide
          mason Mason Meyer (Inactive) added a comment -

          We should also make sure the math operator menu items are followed by "..." to indicate that more input is required.

          Show
          mason Mason Meyer (Inactive) added a comment - We should also make sure the math operator menu items are followed by "..." to indicate that more input is required.
          Hide
          mason Mason Meyer (Inactive) added a comment -

          I am closing this issue because this whole issue is now irrelevant due to the changes requested to the new Graph Track operations user interface in IGBF-617.

          Show
          mason Mason Meyer (Inactive) added a comment - I am closing this issue because this whole issue is now irrelevant due to the changes requested to the new Graph Track operations user interface in IGBF-617.

            People

            • Assignee:
              mason Mason Meyer (Inactive)
              Reporter:
              mason Mason Meyer (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: