RowItem: Fixed v_extents initial conditions

Using (0, 0) as initializers for the global extent calculation
is suboptimal as it causes the lowest y coordinate to always be 0
when all traces have positive y offsets. When moving all traces
down, the scroll area becomes too large as a result. Using
(INT_MAX, INT_MIN) instead fixes this.

diff --git a/pv/view/rowitemowner.cpp b/pv/view/rowitemowner.cpp
index 625620ed0dbe2d074d82764cd6bbd47f3f8e0fed..8970f45a73727207fae763043efbb6df66467c21 100644 (file)
--- a/pv/view/rowitemowner.cpp
+++ b/pv/view/rowitemowner.cpp
@@ -94,7 +94,8 @@ RowItemOwner::const_iterator RowItemOwner::end() const
 
 pair<int, int> RowItemOwner::v_extents() const
 {
-       pair<int, int> extents(0, 0);
+       pair<int, int> extents(INT_MAX, INT_MIN);
+
        for (const shared_ptr<RowItem> r : child_items()) {
                assert(r);
                if (!r->enabled())