lhe, I noticed that in a screenshot from someone else. I can't reproduce it though, so currently have no idea why those font sizes would be the wrong way around.

Yes, I can confirm that for each leg the first waypoint is in a much larger font than the second one. This is on an iPad Air with iOS 8.1.

Actually, I don't mind a visual distinction between first and second waypoint but the difference is a bit too dramatic, and maybe there are better ways to separate them visually.

-- Chris.

Weird, on our iPad Air it appears as it should. Anything unusual about the font settings on the iPad Air in question?

I just checked again and noticed that I got it wrong in my previous post. It's the second waypoing for each leg that's printed larger. Actually, I like it this way since it distinguishes nicely between start and end of each leg. And the second waypoint in one leg is the first waypoint of its successor. Also, it is always toward the second waypoint in a leg that you fly and navigate toward. Therefore, according to my book, you got it right.

-- Chris.

Yes, that is the intended behaviour.

The starting and ending waypoints for each leg do not scale equally. In some cases the starting waypoint will be printed larger – sometimes very much so. I've enclosed pdf files with three PLOG examples. Each of these are printed by the PC version of SkyDemon 3.2.0 on A4 paper with 10 mm margins all around, either landscape, portrait or two per page.

You can clearly see that the starting waypoint name doesn't scale correctly. In the two per page case, it's actually a bit silly.

Another thing is that in the two per page case, the text is generally much smaller in proportion to the space available than in the other cases. I would expect the two per page PLOG to be more or less a scaled-down version of the portrait PLOG, but it's not – the text has been scaled down more than the boxes.

In previous versions, the two per page PLOG was much easier to read. I enclose an example of this from version 3.1.0. Again A4 paper and 10 mm margins all around. (Unfortunately, I only have a Mac install of 3.1.0 and I didn't manage to generate a PDF file on the Mac, so you'll get a screen dump - but that's enough to show the difference.)

A final comment: I don't see the need to include the first waypoint of a leg at all. It is completely redundant as you can find it on the line above – except for the very first leg, but then there is space to print the starting waypoint to the left of the column headings. I feel that including the first waypoint on every line wastes space and clutters the PLOG. Also, if you simply remove the code to print the first waypoint you don't have to debug the scaling problem. :-)

Ok, thanks for persevering. I've located the bug causing the waypoint text sizes to be wrong and fixed it. It's all down to what happens when you ask SkyDemon to show more columns than can comfortably fit, especially when you're asking it to fit them into an A5 space. I've also tweaked the table generation so it reduces the cell padding a little for A5 printing, which will help things fit without shrinking the font size more than necessary.

I have just updated to 3.2 on my PC. The printed plog font used is now much smaller than it was and too small for me to read without glasses. As way of demonstration of the size reduction, SD used to print 3 columns of radio frequencies across A4 landscape, now it prints 4 columns.
Please have a thought for those of us who are asking for help to delay the need for bi-focals!!  

That is interesting. Some people are reporting that the font is too big, some are reporting that it's too small

The font is 12 point in the current version, but because of reports that it's too big we have reduced it to 11 point for the next version. SkyDemon reduces it further for each column if the contents don't fit.
The old PLOG drawing routine was quite naïve in that it used 2 columns if portrait and 3 if landscape, the new one outputs as many columns as will fit, where each column is 60mm wide. This accommodates A5 and other paper sizes properly.

Kevin, I don't suppose you could attach a scan of the landscape print output you have issue with?

Tim,
Now that the bug has been identified, I'm assuming we'll get the fix at the next update?
Hugh

Regards



Hugh

G-OIBM

Commander 114