Issue 19029 - font artifacts left on screen after deleting char and passing over with cursor
Summary: font artifacts left on screen after deleting char and passing over with cursor
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: Other Linux, all
: P2 Trivial (vote)
Target Milestone: OOo 1.1 RC
Assignee: christof.pintaske
QA Contact: issues@gsl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-03 21:30 UTC by khendricks
Modified: 2003-09-05 15:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
screenshot before problem (35.97 KB, image/png)
2003-09-03 21:31 UTC, khendricks
no flags Details
screen shot after random char deletion and passing cursor over it (28.84 KB, image/png)
2003-09-03 21:32 UTC, khendricks
no flags Details
screen shot of artifacts gone after forced screen redraw (28.62 KB, image/png)
2003-09-03 21:32 UTC, khendricks
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description khendricks 2003-09-03 21:30:39 UTC
Hi, 
 
Sorry to be a pain here but I thought someone might want to look at this before RC4 goes out (at 
least before 1.1.0 goes out) ... 
 
I can create a test document (with any proportional font) and then  
randomly delete characters in any one line and then move the cursor 
back and forth across the line near where the character was deleted and I can  
create (reapeatedly) a trail of little artifacts and pieces of characters left  
over all along where the cursor has passed. 
 
This happens with every proportional font I have tried. 
 
If I create a new window and pass it OOo window forcing a redraw all of the  
artifacts and pieces go away. 
 
I have attached a series of pngs that illustrate the problem. 
 
before.png - shows simple lines of text before I start deleting random  
chars and moving the cursor along 
 
after_editing_see_the_artifacts.png - shows what the line looks  
like after editing it  
 
after_forcing_screen_redraw.png - shows what the result was after passing  
another xterm over the garbage area to see what it looks like. 
 
This problem makes OOo almost unusable since I can't tell what I have edited  
as I move the cursor along and it leaves a horrible trail behing it. 
I literally have to take another xterm and pass it over the OOo window to see  
what I have actually done to the line. 
 
This is with the very very latest RC4.  I never noticed this problem until I  
had lots of little single char edits to do in a document and started deleting  
chars in different palces in a line as I moved the cursor along the line to  
the next place to delete. 
 
I hope this is easy to fix! 
 
Kevin
Comment 1 khendricks 2003-09-03 21:31:27 UTC
Created attachment 8984 [details]
screenshot before problem
Comment 2 khendricks 2003-09-03 21:32:06 UTC
Created attachment 8985 [details]
screen shot after random char deletion and passing cursor over it
Comment 3 khendricks 2003-09-03 21:32:48 UTC
Created attachment 8986 [details]
screen shot of artifacts gone after forced screen redraw
Comment 4 khendricks 2003-09-04 02:32:37 UTC
Hi,  
  
Just to make the instructions on how to reproduce it clearer:  
  
On a Linux build:  
  
1. enter a long line of text using any proportional font in Writer  
  
2. Move the cursor into that line of text  
  
3. delete a  char using the delete key   
  
4. start moving the cursor farther down the sentence using the arrow keys  
  
5. repeat steps 3 and 4 and you should begin to see a trail of pieces  
of characters and stange artifacts left behind as the cursor is moved.  
  
It almost seems as if the character under the cursor is being redrawn incorrectly as  
the cursor passes over after a deletion has been made.  
  
Hope this helps to recreate this.  
  
Kevin  
   
Comment 5 philipp.lohmann 2003-09-04 09:37:49 UTC
I just installed RC4, but i cannot reproduce it; my system is SuSE
8.2; XFree4.3.0 (with RENDER of course); i tried a libfreetyp.so.6.3.3
as well as a libfreetype.so.6.3.2 and used Bitstream Vera Serif as
well as Bitstream Vera Sans trying to reproduce this.

Apart from OOo itself i could imagine either the RENDER code itself or
freetype being responsible for this; from you mails on releases.ooo i
gather that you are using XFree4.3.
Comment 6 khendricks 2003-09-04 13:23:45 UTC
Hi, 
 
Closing this as INVALID since the bug is not in OOo but in the Radeon driver that is 
part of XFree86 4.3.0.  Once I converted to the old/slow "fbdev" driver the artifacts 
went competely away and OOo looks wonderful! 
 
Sorry for the false alarm but I never saw this on earlier builds and so I thought it must 
be OOo related and not XFree86 driver related. 
 
Thanks, 
 
Sorry to be such a pain here. 
 
Kevin 
 
Comment 7 philipp.lohmann 2003-09-04 15:05:23 UTC
I'm relieved that the problem is solved. But i also hope that you
won't be stuck with the fbdev driver for long as it's quite slow :-)
Comment 8 khendricks 2003-09-04 16:22:40 UTC
Hi,  
  
Luck is with me today, it seems if I enable "dri" in my /etc/X11/XF86Config and the  
radeon driver (accelerated), now it all works fine!!!!  
  
So I can be fast and have 3D or slow fbdev and it all works, I just can't be fast with  
dri not loaded.  
  
This is so strange.  Anyway, I helped write some of the acceleration code for the old  
ati mach 64 for the old Xpmac server, so as long as the Radeon is not that much  
different, I should be able to track something down.  
  
Thanks,  
  
Kevin  
  
Comment 9 christof.pintaske 2003-09-05 15:29:12 UTC
closed