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

Pref>tracks list does not update based on +/- status

    Details

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

      Description

      If a track is loaded as two tracks + and , then it populates the pref>track list as two tracks. If these two tracks are combined (/), then the track list still shows two tracks. Reverse is also true - if a bam is loaded as a single track and then the (/-) option is turned off, 2 tracks appear in main view, but only 1 track appears in the track list. Also, if track list does NOT actively update based on the order of the tracks, then it should NOT separate the + and - tracks across the list, keep them sequential.

        Attachments

          Issue Links

            Activity

            Hide
            hiralv Hiral Vora (Inactive) added a comment -

            I don't think that we need any kind of ordering there.

            Show
            hiralv Hiral Vora (Inactive) added a comment - I don't think that we need any kind of ordering there.
            Hide
            alyssa Alyssa Gulledge (Inactive) added a comment -

            Is the list supposed to reflect the order of the tracks as they appear in the main window, or does it reflect the order they are loaded and it should not change the order?

            Show
            alyssa Alyssa Gulledge (Inactive) added a comment - Is the list supposed to reflect the order of the tracks as they appear in the main window, or does it reflect the order they are loaded and it should not change the order?
            Hide
            hiralv Hiral Vora (Inactive) added a comment -

            Fixed in r13273. It would now show only one track.

            Show
            hiralv Hiral Vora (Inactive) added a comment - Fixed in r13273. It would now show only one track.
            Hide
            alyssa Alyssa Gulledge (Inactive) added a comment -

            From a cleared start, when I open TAIR10, and do nothing, it opens as 2tracks. Then I open the pref>tracks tab and each track (+ and ) are listed separately. Changes to one affect both, but they are separate in the list. If I check the +/ box, then the track properly merges, but the list still shows them separately.

            If I then add any other file, it properly merges them in the list

            Show
            alyssa Alyssa Gulledge (Inactive) added a comment - From a cleared start, when I open TAIR10, and do nothing, it opens as 2tracks. Then I open the pref>tracks tab and each track (+ and ) are listed separately. Changes to one affect both, but they are separate in the list. If I check the +/ box, then the track properly merges, but the list still shows them separately. If I then add any other file, it properly merges them in the list
            Hide
            hiralv Hiral Vora (Inactive) added a comment -

            I don't see tracks to be listed twice. Also it is never suppose to show you in that manner.

            Which files do you use for your testing?

            Show
            hiralv Hiral Vora (Inactive) added a comment - I don't see tracks to be listed twice. Also it is never suppose to show you in that manner. Which files do you use for your testing?
            Hide
            alyssa Alyssa Gulledge (Inactive) added a comment -

            Apparently adding in new tracks or deleting tracks WILL cause this correct itself for order and track (+/-) status

            Show
            alyssa Alyssa Gulledge (Inactive) added a comment - Apparently adding in new tracks or deleting tracks WILL cause this correct itself for order and track (+/-) status

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: