You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.
Describe the bug
When the user has multiple tracks, the last track is cut off. As intended behavior, the last track should always be visible regardless of the number of tracks.
To Reproduce
Steps to reproduce the behavior:
Method 1
Open Saucedacity without any projects open.
Go to Tracks > Add New > Mono Track (or Stereo Track, it doesn't matter) and add a couple of new tracks
Observe bug (the last track is cut off)
Method 2
Open any multi-track project
Observe bug (the last track is cut off)
Expected behavior
The last track should be fully visible.
Screenshots
Additional information (please complete the following information):
... with some reinterpretation of what it means to "set the height" of a track.
Changing height allocation for a reduced separator between panels may also
be done, but that logic should also be localized in TrackPanel.cpp.
Cherry picked from audacity/5f7f180
Signed-off-by: Avery King <avery98@pm.me>
(Also big shout-out to Tenacity's commit log for pointing me to these
Audacity commits, especially to akleja. You've done me a huge favor!)
This commit and the last 6 commits resolve dreaded #20. We will now
proceed...
<3
Describe the bug
When the user has multiple tracks, the last track is cut off. As intended behavior, the last track should always be visible regardless of the number of tracks.
To Reproduce
Steps to reproduce the behavior:
Method 1
Method 2
Expected behavior
The last track should be fully visible.
Screenshots
![Saucedacity with a track cut off at the bottom of the window](https://user-images.githubusercontent.com/58306640/144771484-c56c8093-54f6-4c11-8011-ccd716fb1f34.png)
Additional information (please complete the following information):
Additional context
This bug was originally reported by @gotsum over at our Discussions page. We thank you for your report.
The text was updated successfully, but these errors were encountered: