Bug 44008 - EDITING: Caret not rendered correctly when anti-aliasing disabled.
Summary: EDITING: Caret not rendered correctly when anti-aliasing disabled.
Status: RESOLVED DUPLICATE of bug 55142
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86 (IA32) macOS (All)
: high critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-21 03:39 UTC by dupei2sise
Modified: 2012-09-26 09:41 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
LO - Sample (150.19 KB, image/jpeg)
2012-06-05 14:47 UTC, dupei2sise
Details
LO - Text (198.90 KB, image/jpeg)
2012-06-05 14:48 UTC, dupei2sise
Details
NeoOffice - Text (187.57 KB, image/jpeg)
2012-06-05 14:48 UTC, dupei2sise
Details
NeoOffice - Sample (148.92 KB, image/jpeg)
2012-06-05 14:49 UTC, dupei2sise
Details
Pages - Text (151.11 KB, image/jpeg)
2012-06-05 14:49 UTC, dupei2sise
Details
Pages- - Sample (110.16 KB, image/jpeg)
2012-06-05 14:50 UTC, dupei2sise
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dupei2sise 2011-12-21 03:39:25 UTC
Caret is not being rendered correctly while typing if you disable text antialiasing inside LibreOffice via preferences dialog or directly in Mac OS (albeit using TinkerTool to remove anti-aliasing up to 144pt sizes).

When typing the first few characters, the caret stays adjacent to the last typed character as it should, but when the text reaches the middle of the page or so, the caret starts to move farther away from the last typed character until it looks as though there are several spaces between the typed character and the caret.

When you press Enter to move to a new line, the caret is again OK for the first few characters but then it starts moving away.

There are also small artifacts sometimes - it looks as though the typed text moves a bit left (a pixel or two) and looks really ugly and unreadable (using Times New Roman 12pt). With aliasing the text is too blurry and LO is unusable :-(.

APP: LibreOffice 3.4.4 & LibreOffice 3.5.0 beta 1 are affected.
OS: Snow Leopard 1.6.8.
Comment 1 dupei2sise 2011-12-30 01:43:21 UTC
When anti-aliasing is off and you turn on "Nonprinting Characters" on the View menu, the caret is then rendered correctly after the last character, but the entire line of text is "breathing" while you type - the characters move slightly left and right, so that would actually be a second bug. 


Changed to blocker because Writer is really unusable when anti-aliasing is turned off in settings, and the font is too blurry when anti-aliasing is on.

I've checked the last version of OpenOffice for Mac that I could find - OOo 3.3.0 and the same thing happens in that version, so it's an inherited bug.

HTH.
Comment 2 Petr Mladek 2012-01-04 07:48:02 UTC
I understand that it is very annoying, so I add some developers into CC who might be able to help.

On the other hand, it seems to be very old bug and people have lived with it for years. Such bugs can't block the release => lovering the severity a bit.
Comment 3 dupei2sise 2012-01-11 04:51:34 UTC
Thanks. 

Still new to all this bug reporting stuff so I messed up on the severity part, sorry. 

Hopefully other LO users on the Mac platform are "living with it". I've had to move back and do my writing on a Win PC (LO) because of this. 

Pages '09 is buggy and useless, Mac Word is not worth the money, and even if it was, wouldn't use it.

Thanks again.
Comment 4 Joan Carles Batalla 2012-01-17 09:19:29 UTC
I'm a newcomer both to bug report and mac (portable). I come from Ubuntu. In fact my desktop is and hope will be, ubuntu.

LibreOffice has been my first mac application installation. The first thing I noticed has been this "line-you-are-editing shaking". I've been a little surprised reading that this is an "old" bug and people have learnt to live with it.

I find this bug quite annoying but anyway, LibreOffice is a "libre" choice and hence this error is assumed as long as I will not install MAC soft and I'm used to LibreOffice already.

Thanks for your work.

PS: For newcomers to MAC using OWA. Give a look to (free) DavMail (excellent).
Comment 5 Florian Reisinger 2012-04-10 00:15:23 UTC
It would be nice to have this checked...
Try with this: http://ftp.uni-muenster.de/pub/software/LibreOffice/stable/3.3.0/mac/x86/?C=S;O=D

If it is a really old bug, please test with old OpenOffice build: (Oldest for Mac I found): http://ftp.rz.tu-bs.de/pub/openoffice-archive/stable/2.1.0/
and change to the oldest version affected
(Curerently 3.4.4)
Comment 6 dupei2sise 2012-06-05 14:47:28 UTC
Created attachment 62601 [details]
LO - Sample
Comment 7 dupei2sise 2012-06-05 14:48:20 UTC
Created attachment 62602 [details]
LO - Text
Comment 8 dupei2sise 2012-06-05 14:48:54 UTC
Created attachment 62603 [details]
NeoOffice - Text
Comment 9 dupei2sise 2012-06-05 14:49:20 UTC
Created attachment 62604 [details]
NeoOffice - Sample
Comment 10 dupei2sise 2012-06-05 14:49:42 UTC
Created attachment 62605 [details]
Pages - Text
Comment 11 dupei2sise 2012-06-05 14:50:05 UTC
Created attachment 62606 [details]
Pages- - Sample
Comment 12 dupei2sise 2012-06-05 14:52:42 UTC
(In reply to comment #5)
> It would be nice to have this checked...
> Try with this:
> http://ftp.uni-muenster.de/pub/software/LibreOffice/stable/3.3.0/mac/x86/?C=S;O=D
> If it is a really old bug, please test with old OpenOffice build: (Oldest for
> Mac I found): http://ftp.rz.tu-bs.de/pub/openoffice-archive/stable/2.1.0/
> and change to the oldest version affected
> (Curerently 3.4.4)

3.3.0 -> the same as 3.5.4
2.1.0 -> not working, I get "script timed out" error and an empty bash window
Comment 13 Florian Reisinger 2012-06-06 07:18:40 UTC
Ok, I change it to the oldest version affected (The first LibreOffice). Due to the fact I do not have a Mac I can't do any further resaerch...
Comment 14 Roman Eisele 2012-09-25 18:24:25 UTC
I *think* that this is the same issue as reported in bug 55142. If this is true, there are good news: bug 55142 is fixed in master.

I mark this as a duplicate of bug 55142.

@ dupei2sise:

It would be wonderful if you could please check with a current master build (available from
   http://dev-builds.libreoffice.org/daily/MacOSX-Intel@1-built_no-moz_on_10.6.8/master/current/
if the present problem is fixed or at least substantially improved now ...

Thank you!

*** This bug has been marked as a duplicate of bug 55142 ***
Comment 15 Roman Eisele 2012-09-26 09:41:06 UTC
I wrote:

(In reply to comment #14)
> I *think* that this is the same issue as reported in bug 55142. If this is
> true, there are good news: bug 55142 is fixed in master.

Sorry:
I was a bit too fast here, because the fix might have introducet one or two regression(s), so it is not yet clear if the issue is really fixed. So please wait a bit until we know more about the success of the fix for bug 55142.