On Sunday 05 September 2004 09:56, Silvan wrote:
> On Sunday 05 September 2004 02:33 am, Richard Bown wrote:
> > RH9:
> >
> > rosegardenconfigurationpage.h:38:28: kfontrequester.h: No such file or
> > directory In file included from notationstrings.cpp:29:
>
> Taking off-list because I can't be bothered to upload these pixmaps to my
> web site, but I don't want to mail them to everyone on rg-devel either, and
> put up with the damn message being rejected.
I'm putting it back to the list since Chris is involved as well.
> /usr/include/kde/kfontrequester.h
>
> I don't see the usual "This has been around since version X.Y" for this.
> Searching KDE API docs online and manually changing the URL to flip between
> 3.1 and 3.2, it looks like this showed up in 3.2
Yes, it did, I'm fixing this right now.
> I'll leave it between you and Guillaume to duke it out over whether we want
> to up the ante and demand 3.2 now.
I don't know how widely 3.1 is still used, really. That Rich still uses it
would indicate that requiring 3.2 is still a bit premature, although most of
the KDE software I've downloaded recently does.
> It may be a moot point. It didn't actually achieve anything positive
> anyway. I played with the new font picker GUI and tried a number of
> different fonts, all of which were capable of going up to 64 points. I
> always got results similar to the attached screenshot. Not only are the
> elements in question still utterly absent from the print preview
> (delete-this1.png), but this has the added bonus effect that the main
> notation view itself is now fucked up. (Notice the fonts cut off.)
Yes, I see that too. I was so focused on printing that it completely escaped
me. Actually the reason may be because we're misusing QFontMetrics. We always
use it the QFontMetric(QFont) ctor, but according to the docs we should be
using QPainter::fontMetrics(). However that's not compatible with the way we
create text pixmaps, since we use the font metrics to determine the size of
the pixmap we're going to draw the text on in the first place.
> Previously, the font problems were limited to print/preview only, and the
> notation view display was fine for all elements, including elements that
> didn't print or preview correctly.
>
> Just for shits and giggles, I picked out the original fonts. Well,
> actually, I picked Times and Charter. I couldn't remember what the other
> one was. Schoolbook. Century. Something. Anyway, two bitmap fonts that
> could only go up to 29 points. The result on screen in the notation view
> was that the fonts are still cut off, but they just look shitty now.
> (delete-this2.png)
I probably broke NotePixmapFactory::drawTextAux(). Will fix.
> Now for more shits and giggles, I've tried Arial and Verdana at 14 points
> each. (delete-this3.png) Now more is cut off than before, it looks like
> to me.
>
> But it wasn't the point size, because switching for Times New Roman and
> Book Antiqua at 4 points each, I got no obvious change (delete-this4.png)
Forget the point size, it's irrelevant in this situation. The font requester
is only used to set a font family actually, the choosen size is ignored (not
perfect I know, but still manageable).
--
Guillaume.
http://www.telegraph-road.org
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
