I apologize for being so slow to answer.<br><br>The polygon border problem should be fixed. Like the lines, it only matches when both the map and legend are in render mode.<br>I think there are time when it's good to be able to set render mode
independently, but it would be helpful to have a "set all items to
render/set all items to cache" option.<br><br>
The label positioning is slightly more difficult, and I haven't had time to work on it. Thanks for the dataset though.<br>As far as I can tell, the font nastiness occurs with Qt on Ubuntu. I've created a simple test program which reproduces the problem, so it's not a QGIS bug:
<br><br><div style="margin-left: 40px;" id="mb_5"><div style="direction: ltr;"><span class="q">Steven Bell wrote:<br><br>> If some other Linux users could run my <span id="st" name="st" class="st">font</span> test <span id="st" name="st" class="st">
program</span> below, that<br>> would be helpful. Let me know your Linux distro, <span id="st" name="st" class="st">Qt</span> version, and<br>> whether the text came out garbled.<br>> A Linux binary is here: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://botsnlinux.googlepages.com/QT_Fonts" target="_blank">
http://botsnlinux.googlepages.com/QT_Fonts</a> , and<br>> source code is here: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://botsnlinux.googlepages.com/QT_Fonts.zip" target="_blank">http://botsnlinux.googlepages.com/QT_Fonts.zip
</a><br>> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://botsnlinux.googlepages.com/QT_Fonts.zip" target="_blank">http://botsnlinux.googlepages.com/QT_Fonts.zip</a>><br><br></span></div><div style="direction: ltr;">
I have this terrible compulsion to convert <span id="st" name="st" class="st">Qt</span> C++ code into Python/<span id="st" name="st" class="st">Qt</span><br>code, so my Python version of Steven's code is here:<br><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.maths.lancs.ac.uk/%7Erowlings/Geog/Qgis/QT_Fonts_Python.zip" target="_blank">http://www.maths.lancs.ac.uk/~rowlings/Geog/Qgis/QT_Fonts_Python.zip</a>
<br><br>[files unzip into current directory so unzip this in a sub-folder of its<br>own. there's only three files in it]<br><br> unzip, run "python main.py" and if you have PyQt4 it should do the<br>same as Steven's C++ example - ie on my Ubuntu box show text badly when
<br>scaling small point fonts up to large pixel sizes.<br></div><div style="direction: ltr;"><span class="sg"><br>Barry<br></span></div></div><br>I added a bit of code which checks the default font size and limits it to a minimum of 6. With some settings, we were getting sizes around 3, which was totally unreadable. 6 may still be too small, but at least it's a little better.
<br>Also, I think I have fixed a bug which sometimes prevented the addition of more than one map to the page.<br>Steven<br><br><br><div><span class="gmail_quote">On 7/29/07, <b class="gmail_sendername">Maciej Sieczka</b> <
<a href="mailto:tutey@o2.pl">tutey@o2.pl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">>>> Maciej wrote:<br>
>> Maciej wrote:<br>> Paolo wrote:<br>Steven Bell wrote:<br><br>> Hi all, Thanks once again for your testing.<br><br>Cheers!<br><br>I'm just back from a short vacation on a rainy Baltic coast. It was<br>cool (indeed).
<br><br>>>> However, either in "cache" or "render" mode in the *map<br>>>> composer* line widths on the legend and on the map *do not<br>>>> correspond*. On the legend it's always thicker.
<br><br>> This is a known problem for cache mode, since the cache is created<br>> at a variable resolution and then variably scaled. In render mode,<br>> the line widths appear to correspond.<br><br>You are correct. The reason why I thought that the line width on the
<br>the lengend and on the map don't correspond in render mode for me<br>either, is that I have just found out that one has to turn on the<br>render mode *separately* for the legend and the map. I didn't know that
<br>before. So my fault. However, IMO it's questionable if switching<br>between the render and cache mode should be print-composer-wise, or<br>sperate for the legend and the map as it is currently. What do you think?<br>
<br><br>> I'll try to look into it more when I get a chance (unfortunately,<br>> that may be a few weeks).<br><br>No problem at all. I'm glad you might be interested in looking into it.<br><br>>> the border of polygons however it is not synchronized between
<br>>> legend and map<br><br>> I changed the line for the polygon outline to be a "cosmetic pen"<br>> (1px wide, regardless of scale) when the line widths were getting<br>> out of hand. Since that should be fixed now, I can probably put the
<br>> original line widths back.<br><br>I think that it would be consistent this way. If one really wants 1px<br>wide border for his polygons on the printout, he can set the border<br>width to 0 in the project.<br><br>
>>>> 2. labels placement and size in the map canvas not always<br>>>>> corresponds to that in the map composer and printout<br><br>>>> Still valid. See the following attachments:<br>>>>
<br>>>> labels_mapview.png labels_composer.png labels_pdf.png<br>>>><br>>>> They show how the labelled points look in the QGIS map view, map<br>>>> composer and in the output pdf, respectively. Each looks much
<br>>>> different. Could it be at least fixed so that the view in the<br>>>> map composer and the resulting pdf looked similar?<br><br>> I haven't done much testing with vector labels, so I'm not too
<br>> surprised some bugs still lurk there. If you could send me some<br>> simple projects which reproduce the problem, that would be great<br>> help.<br><br>Please find the points shapefile attached. It's from the free
<br>"Spearfish" GRASS dataset (BTW, the new "Save as shapefile" worked<br>great for the original GRASS vector layer!). Display labels from field<br>'str1' and try to print.<br><br>I'm not sending you the project with labels set on, as it shows there's
<br>a bug that once you set labels on, save the project and reload it, the<br>labels are not displayed anymore and I can't find a way to make them to<br>- besides starting the project from scratch again.<br><br>>>>> 3. vector point symbols get rasterized in the printout
<br><br>>>> Still an issue. Is it fixable?<br><br>>> moreover, point size is much larger (1.4x? 2x?) in the legend than<br>>> in the map, and larger in the pdf.<br><br>> Unfortunately, I don't think we can fix this for
0.9. It will<br>> require some significant changes to the symbology and rendering,<br>> which has the potential to break things.<br><br>Really too bad. This is quite an issue.<br><br>>>>> 4. irregular letter spacing in the printout
<br><br>>>> Still the case. See the attachment spacing_pdf.png. Moreover,<br>>>> layer's name is to close to categories' names below, overlapping<br>>>> it a bit.<br>>>><br>>>> Also, in the composer *the very same legend* before printing to
<br>>>> pdf looks completely different (font_composer.png) and rather<br>>>> corrupted. Can this avoided? What's strange, if I zoom in in the<br>>>> map composer once or twice, the legend's font starts looking
<br>>>> same as in target pdf, hmm. The same problem applies to<br>>>> scalebar.<br><br>> The ugly font bug strikes again! What operating system and Qt<br>> version are you using?<br><br>Ubuntu Dapper, QT
4.3 built from source (qconfig.pri attached in case<br>it matters what features where compiled).<br><br>> I have exactly the same problem, and I don't think there's much we<br>> can do. (I'm running Ubuntu with Qt
4.2/4.3)<br><br>So a QT bug?<br><br>>>> Another, smallish, issue which remains is that the default font<br>>>> size for legend "6" is always too small too be any readable. I<br>>>> guess defaulting to at least 8 is a better idea.
<br><br>>> agreed. also, default font (sans-serif?) does not appear optimal<br>>> on many machines.<br><br>> I'm pretty sure Qt provides the default font, so we'd have to<br>> manually override this. I'll see if we can do this in a simple,
<br>> cross-platform way. The font size is calculated based off of the map<br>> scale, and often is less than 6. Perhaps some code to limit the<br>> default to a minimum of 8 would be helpful.<br>><br>> I'm not going to have much time to work on QGIS in the next few
<br>> weeks, but I'll try to fix what I can for 0.9.<br><br>Understood. Many thanks for getting the print composer rolling again<br>and good luck.<br><br>Maciek<br><br><br>#configuration<br>CONFIG += no_mocdepend release stl qt_no_framework
<br>QT_ARCH = i386<br>QT_EDITION = OpenSource<br>QT_CONFIG += qt3support accessibility opengl minimal-config small-config medium-config large-config full-config reduce_exports ipv6 clock-monotonic mremap getaddrinfo ipv6ifname getifaddrs system-jpeg system-png png system-tiff system-freetype system-zlib nis cups iconv glib openssl x11sm xshape xinerama xcursor xfixes xrandr xrender fontconfig tablet xkb release
<br><br>#versioning<br>QT_VERSION = 4.3.0<br>QT_MAJOR_VERSION = 4<br>QT_MINOR_VERSION = 3<br>QT_PATCH_VERSION = 0<br><br>QMAKE_RPATHDIR += "/usr/local/qt4/lib"<br><br><br></blockquote></div><br>