Bug 61534 - Red error messages appear in C++ program window
Summary: Red error messages appear in C++ program window
Status: RESOLVED DUPLICATE of bug 53392
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: SVN
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 64058 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-07-22 14:08 UTC by Ian Wadham
Modified: 2003-11-29 14:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Wadham 2003-07-22 14:08:42 UTC 
Version:           3.0.0a4 (using KDE 3.1.1)
Installed from:    SuSE
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:          Linux (i686) release 2.4.20-4GB

Sometimes the red error messages from the Messages window appear in the top of the C++ program file window (repaint prob?).  When you scroll that part of the program window out of sight and scroll it back into view, the displayed lines return to normal.
Comment 1 Jens Dagerbo 2003-08-21 19:47:31 UTC 
Repeatedly reported katepart repaint bug.
Comment 2 Jens Dagerbo 2003-09-11 14:30:36 UTC 
*** Bug 64058 has been marked as a duplicate of this bug. ***
Comment 3 Jens Dagerbo 2003-11-03 19:05:02 UTC 
I don't know why we still have this set to kdevelop. Reassigning.
Comment 4 Christoph Cullmann 2003-11-03 21:01:46 UTC 
after changing kateviewinternal to use a other methode for doublebuffering and only opening one qpainter for the whole repaintEvent, this kind of redraw errors has dissapeared on my system, reopen the bug is somebody can still reproduce them
Comment 5 Hamish Rodda 2003-11-04 07:06:50 UTC 
Nope, still present.

I will make the necessary changes to kdevelop to work around this (hide view _before_ moving it) as the real fix in qt may never happen...
Comment 6 Hamish Rodda 2003-11-29 14:37:23 UTC 
Good news, this is fixed in cvs, hooray!

*** This bug has been marked as a duplicate of 53392 ***