summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim E. Real <termtech@rogers.com>2010-11-18 00:17:40 +0000
committerTim E. Real <termtech@rogers.com>2010-11-18 00:17:40 +0000
commit5fbe9de014fad31ba65d955e86904757322cf212 (patch)
tree57efba852229a668144da8a8a09b917c8fea4b71
parente7b8a42ef4001083c1028369daf5ab1cc2e6c9c7 (diff)
Removed a fix which cured graphic corruption for me in MusE-1. Not required now.
-rw-r--r--muse2/ChangeLog2
-rw-r--r--muse2/muse/widgets/view.cpp25
2 files changed, 3 insertions, 24 deletions
diff --git a/muse2/ChangeLog b/muse2/ChangeLog
index 0bd63d4f..60c10f66 100644
--- a/muse2/ChangeLog
+++ b/muse2/ChangeLog
@@ -1,3 +1,5 @@
+17.11.2010
+ - Removed a fix which cured graphic corruption for me in MusE-1. Not required now. (Tim)
16.11.2010
- Fixed track info sizing problems. In Arranger::switchInfo() added tgrid->update(). (Tim)
QLayout::update() seems to be a new method, we needed to call it here.
diff --git a/muse2/muse/widgets/view.cpp b/muse2/muse/widgets/view.cpp
index 75116415..35208b1b 100644
--- a/muse2/muse/widgets/view.cpp
+++ b/muse2/muse/widgets/view.cpp
@@ -139,30 +139,7 @@ void View::setYPos(int y)
}
else { // shift down
bitBlt(&pm, 0, delta, &pm, 0, 0, w, h-delta, true); // CopyROP, true); ddskrjo
-
- // NOTE: June 2 2010: On my machine with an old NV V8200 + prop drivers (curr 96.43.11),
- // this is a problem. There is severe graphical corruption in some of the view-based windows.
- // Not just here but several other windows (ex. ladspa browser).
- // I believe (?) I saw other QT3 apps exhibit this problem, too. QT4 apps don't do it.
- // Neither does it happen when xorg drivers used.
- //
- // However, there is one type of MusE corruption which ALL drivers seem to show, and that is
- // the arranger 'grey' non-part-based tracks (Input, Output, Group etc.).
- // It is also observed on another machine with an ATI card and a different linux distro.
- // This change also fixes that problem, although the fact that xorg drivers show the problem
- // had long made me believe that it was our drawing technique, not particularly this line.
- // Meaning that perhaps this line is not the right way to fix that problem.
- //
- // On the other hand the two problems may be related, and only one shows with xorg drivers...
- // Ultimately it could just be my NV card, as a request for similar experience in mail list
- // returned all negative.
- //
- // FIXME: This change cures it for me, but we shouldn't leave this in - shouldn't need to do this...
- //
- //r = QRect(0, 0, w, delta);
- // Changed p3.3.43
- r = QRect(0, 0, w, h);
-
+ r = QRect(0, 0, w, delta);
}
QRect olr = overlayRect();
QRect olr1(olr);