Project

General

Profile

Bug #579

Monospaced font not wrapped correctly

Added by mstormo almost 16 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Quassel GUI (Qt)
Target version:
-
Start date:
02/24/2009
Due date:
% Done:

100%

Estimated time:
Version:
0.4.0
OS:
Windows

Description

When I use a monospaced font in the chat window, the text is not wrapped correctly, and there's no scrollbars, so I can't see the whole text.

Associated revisions

Revision 12fa4e53 (diff)
Added by Manuel Nickschas over 15 years ago

Workaround the wordwrap issues with Qt

This is a real fugly workaround for Qt bug 238249. As long as it makes Quassel wrap words correctly,
I'm willing to live with it though.

There's still some pathological cases where we still get it wrong (long URLs with real narrow columns,
apparently), but meh.

Closes #579, closes #704.

History

#1 Updated by Sputnick over 15 years ago

  • Status changed from New to Assigned
  • Assignee set to Sputnick
  • Target version set to 0.5.0
  • % Done changed from 0 to 80

Looks like the recent changes in our layout engine might workaround this Qt bug and solve the problem for Quassel users. We'll see. Reopening this so I won't forget.

#2 Updated by Sputnick over 15 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 80 to 100

#3 Updated by clopez over 11 years ago

  • Status changed from Resolved to Feedback
  • Target version changed from 0.5.0 to 33
  • % Done changed from 100 to 50

Hi.

I'm running quassel-client 0.8.0 on Debian/Wheezy and this issue still happens. Perhaps is a regression.

If I configure monospace font the text is not wrapped correctly and I can't read long lines.

#4 Updated by clopez over 11 years ago

Ok... After closing&reopening quassel-client now seems to work as expected.

could be this caused for changing the fonts several times without restarting the program?

#5 Updated by Anonymous over 11 years ago

yes. it's too lazy to properly trigger a re-{draw,layout} when changing certain properties (scrolling up or switching buffers may be a viable workaround); a full restart after changing stuff is somewhat expected. there may or may not be tickets relating to it directly.

#6 Updated by clopez over 11 years ago

Thanks for the information.

After several days of continuous use I confirm that the issue not longer happens after restarting it. All seems to works as expected.

Feel free to close this.

#7 Updated by Anonymous over 11 years ago

  • Status changed from Feedback to Resolved

#8 Updated by Sputnick almost 11 years ago

  • Target version deleted (33)
  • % Done changed from 50 to 100

Also available in: Atom PDF