Details

    • Story Points:
      1
    • Sprint:
      Winter 4 Feb 8 - Feb 19, Winter 5 Feb 22 - Mar 5, Winter 6 Mar 8 - Mar 19

      Description

      Situation: In IGB, the Track Label Font size dropdown is limited to values between 8-20. This is fine for the default IGB window size, but if a user has a large screen (for example 32 inches and above) and is capturing many tracks, the track labels can appear too small.

      Task: Expand the range of the Track Label Font size.

      Note that the Track Label Font size can be set in multiple locations in IGB: Annotation tab, Graph tab, Annotation Label Font in preferences, Tracks in preferences, Track Defaults in preferences.

      1. IGBF-2770-Expand-range-of-Track-Label-Font-size.pptx
        6.98 MB
        Ann Loraine
      1. 72-2.PNG
        42 kB
      2. Anno_AutoSized.PNG
        71 kB
      3. Anno_Fixed_15font.PNG
        75 kB
      4. Anno_Fixed_48Font.PNG
        66 kB
      5. Font22.PNG
        31 kB
      6. Font28.PNG
        31 kB
      7. Font36.PNG
        34 kB
      8. Font72.PNG
        33 kB
      9. trackLabelFont.png
        63 kB

        Issue Links

          Activity

          Show
          inaylor Irvin Naylor (Inactive) added a comment - Nowlan Freese - Here are the reverted changes: https://bitbucket.org/Inaylor01/integrated-genome-browser/commits/branch/IGBF-2770
          Hide
          nfreese Nowlan Freese added a comment -

          Irvin Naylor - looks good, please create a pull request.

          Show
          nfreese Nowlan Freese added a comment - Irvin Naylor - looks good, please create a pull request.
          Show
          inaylor Irvin Naylor (Inactive) added a comment - Pull request - https://bitbucket.org/lorainelab/integrated-genome-browser/pull-requests/866/igbf-2770-expand-range-of-track-label-font
          Hide
          aloraine Ann Loraine added a comment -

          Please rebase the branch onto the latest master branch.

          Also, please try this:

          Instead of using the Bitbucket "sync" button to bring your fork up-to-date with the team repository, use your local clone as a go-between to update your fork.

          By avoiding the "sync" button, I think we can avoid seeing loads and loads of merge commits, which keeps the project history smaller and easier to read. I recently stopped using "sync" because of that.

          In case this will be helpful, here are some instructions on how to do that. But there are many ways to do the same thing in git, so don't feel like you have to do it exactly this way if you prefer another approach.

          • On your local copy of IGB, switch to the master branch (save any work you have not yet committed by using "git stash")
          • If you have not already done so, add the team repository as a new remote, aliased to the string "upstream" (git remote add upstream https://bitbucket.org/lorainelab/integrated-genome-browser.git")
          • Check that the above command has worked properly by listing your clone's remotes (git remote -v)
          • Update your local master branch using upstream (git pull upstream master)
          • Push the changes up to your fork, which is very likely "aliased" to the string "origin" (git push origin master)

          Now your fork is up-to-date. Yay!
          Next, rebase your branch on the master branch, which is now up-to-date in your clone and your fork. Resolve any conflicts that may come up.

          A tip: Before rebasing, re-play a few of the "learn git branching" rebase animations as a warm-up if you need it.

          Show
          aloraine Ann Loraine added a comment - Please rebase the branch onto the latest master branch. Also, please try this: Instead of using the Bitbucket "sync" button to bring your fork up-to-date with the team repository, use your local clone as a go-between to update your fork. By avoiding the "sync" button, I think we can avoid seeing loads and loads of merge commits, which keeps the project history smaller and easier to read. I recently stopped using "sync" because of that. In case this will be helpful, here are some instructions on how to do that. But there are many ways to do the same thing in git, so don't feel like you have to do it exactly this way if you prefer another approach. On your local copy of IGB, switch to the master branch (save any work you have not yet committed by using "git stash") If you have not already done so, add the team repository as a new remote, aliased to the string "upstream" (git remote add upstream https://bitbucket.org/lorainelab/integrated-genome-browser.git ") Check that the above command has worked properly by listing your clone's remotes (git remote -v) Update your local master branch using upstream (git pull upstream master) Push the changes up to your fork, which is very likely "aliased" to the string "origin" (git push origin master) Now your fork is up-to-date. Yay! Next, rebase your branch on the master branch, which is now up-to-date in your clone and your fork. Resolve any conflicts that may come up. A tip: Before rebasing, re-play a few of the "learn git branching" rebase animations as a warm-up if you need it.
          Hide
          rweidenh Rachel Weidenhammer (Inactive) added a comment -

          Post-Merge testing is complete.

          Following along with the attached PowerPoint slides, I changed the font sizes through the Annotation tab, Graph tab, Tracks in preferences, and Track Defaults in preferences.

          Everything works as expected.

          Moving to closed.

          Show
          rweidenh Rachel Weidenhammer (Inactive) added a comment - Post-Merge testing is complete. Following along with the attached PowerPoint slides, I changed the font sizes through the Annotation tab, Graph tab, Tracks in preferences, and Track Defaults in preferences. Everything works as expected. Moving to closed.

            People

            • Assignee:
              rweidenh Rachel Weidenhammer (Inactive)
              Reporter:
              nfreese Nowlan Freese
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development

                  Agile