Uploaded image for project: 'Bug Repository'
  1. Bug Repository
  2. BUG-470

Track Operations: when a single track is selected, the 'multi track' options should greyed out

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Labels:
      None

      Description

      Currently if you select a single track the multi track operations combo box and apply button are active.

        Attachments

          Issue Links

            Activity

            Hide
            hiralv Hiral Vora (Inactive) added a comment -

            This is not a bug. When you select multiple track and apply unary operation, it is still valid. It applies to individual track.

            Show
            hiralv Hiral Vora (Inactive) added a comment - This is not a bug. When you select multiple track and apply unary operation, it is still valid. It applies to individual track.
            Hide
            alyssa Alyssa Gulledge (Inactive) added a comment -

            BUT you should NOT be able to select 'multi-track' operations if a single track is selected.

            Show
            alyssa Alyssa Gulledge (Inactive) added a comment - BUT you should NOT be able to select 'multi-track' operations if a single track is selected.
            Hide
            lfrohman Lance Frohman (Inactive) added a comment -

            The name is incorrect,
            the difference between the two, is that the unary operations
            will create one new track for each track selected. The
            multiple track (very bad name) operations will only create
            a single new track, now matter how many tracks are selected.
            If there is only one track selected, both of them
            will do the same thing.
            Please try it out, so that you understand, then change the
            name for multiple track. Or I can go over it on the phone with you.

            Show
            lfrohman Lance Frohman (Inactive) added a comment - The name is incorrect, the difference between the two, is that the unary operations will create one new track for each track selected. The multiple track (very bad name) operations will only create a single new track, now matter how many tracks are selected. If there is only one track selected, both of them will do the same thing. Please try it out, so that you understand, then change the name for multiple track. Or I can go over it on the phone with you.
            Hide
            alyssa Alyssa Gulledge (Inactive) added a comment -

            Actually, I still think that 'Multiple track functions' implies that multiple tracks are needed to access the functions you are asking for and return a single track. As such, I don't think the options should change! You should always be offered the same functions under single, and a different set under multiple - that way, there is a reason to separate them AND a user can see the list of options, even if they only have 1 track selected. The dynamic thing is nice in concept, but not in use in this case.

            Single track functions imply that these functions will apply in a 1 to 1 fashion. I would expect that if I selected 2 tracks and asked for 'Copy' from the single track functions, each track would produce a copy - I would get 2 new tracks. I inherently understand this.

            'Multiple track functions' implies that if I selected 2 tracks and asked for 'Sum', I would get 1 track showing the sum of the selected ones; this is also clear.

            However, if I selected a single track, I would expect options that I could perform on one track (Single track functions), but would be confused by the fact that for some reason I can ask for the sum or the mean of a single track (Multiple track options). And there is NO reason to change the offerings! Why offer the same options in two immediately adjacent places? Just keep the multi-track options list, and just gray it out (ie they can see the list, just not select).

            Show
            alyssa Alyssa Gulledge (Inactive) added a comment - Actually, I still think that 'Multiple track functions' implies that multiple tracks are needed to access the functions you are asking for and return a single track. As such, I don't think the options should change! You should always be offered the same functions under single, and a different set under multiple - that way, there is a reason to separate them AND a user can see the list of options, even if they only have 1 track selected. The dynamic thing is nice in concept, but not in use in this case. Single track functions imply that these functions will apply in a 1 to 1 fashion. I would expect that if I selected 2 tracks and asked for 'Copy' from the single track functions, each track would produce a copy - I would get 2 new tracks. I inherently understand this. 'Multiple track functions' implies that if I selected 2 tracks and asked for 'Sum', I would get 1 track showing the sum of the selected ones; this is also clear. However, if I selected a single track, I would expect options that I could perform on one track (Single track functions), but would be confused by the fact that for some reason I can ask for the sum or the mean of a single track (Multiple track options). And there is NO reason to change the offerings! Why offer the same options in two immediately adjacent places? Just keep the multi-track options list, and just gray it out (ie they can see the list, just not select).
            Hide
            lfrohman Lance Frohman (Inactive) added a comment -

            We will disable Multi-Track Operations when only one track is selected.

            Show
            lfrohman Lance Frohman (Inactive) added a comment - We will disable Multi-Track Operations when only one track is selected.
            Hide
            lfrohman Lance Frohman (Inactive) added a comment -

            fixed
            rev 12111

            Show
            lfrohman Lance Frohman (Inactive) added a comment - fixed rev 12111

              People

              • Assignee:
                Unassigned
                Reporter:
                alyssa Alyssa Gulledge (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: