[LOGic] LOGic7 and LOGic 8 Report Differences - Solution

Bill K1UQ k1uq at comcast.net
Sun Mar 12 15:15:13 EST 2006


OOPS - my Fat Finger Medication apparently wore off...

"This is primarily a result of PDA now making use of a better report writer,
known as the C renderer"  should read: "...known as the Windows GDI+
renderer"

Apologies for any confusion!

Regards, Bill K1UQ 


-----Original Message-----
From: logic-bounces at mailman.qth.net [mailto:logic-bounces at mailman.qth.net]
On Behalf Of Bill K1UQ
Sent: Sunday, March 12, 2006 2:19 PM
To: logic at mailman.qth.net
Cc: 'PDA'
Subject: [LOGic] LOGic7 and LOGic 8 Report Differences - Solution

I have sorted out the problems encountered with transporting QSL card
reports created in LOGic 6, moved to LOGic 7 (both of which worked OK) and
ultimately brought into LOGic8.

 

BACKGROUND -

My reports (reverse design of QSL card) have a lot of info in a little
space. Consequently when the report landed in LOGic8, data was wider than
the report form fields and I could not control the precision in LOGic8 as
well as I could in previous LOGic versions.

 

This is primarily a result of PDA now making use of a better report writer,
known as the C renderer.  PDA and I traded emails with a suggestion from
Dennis on how I might regain this lost precision.  What I noted when making
use of the Windows GDI+ renderer was although the units of measure (inches)
allowed for three decimal place precision, I was not allowed to
increment/decrement in one-thousandths of an inch (i.e. 0.001 inch, or 1
mil).  Dennis suggested I switch to pixels and give it a try.  (Thanks, OM
!!)

 

With the contest season just ended, my ability to refocus on this has
provided the following observations and results:

 

 

UNITS OF MEASURE -

Yes, switching to pixels did afford increased precision albeit still not
what it could be. I'd prefer to work in mils.

 

I was able to both increase as well as relocate (left-right) the location of
the form fields and still retain the same type/size font (Courier New, Bold,
7pt).

 

I made use of the new Windows GDI+ renderer tool to alter one field at the
top of each column, then revert to the old way to resize (widen) and align
(left) as accustomed to in LOGic7.

 

PRINTING -

I found I needed to change my printer sheet size and the units of measure
were pixels - from the above step.  With the report altered using pixels as
the unit of measure and with the report saved, I changed the unit of measure
to inches and resized my sheet.  I saved and printed and everything works,
with no more undersize fields, etc.

 

 

RESEARCH -

I did a lot of Google searches to try and learn the differences in how
Windows GDI+ processes fonts and found a new "cottage" consulting industry
has appeared.  Between that and Microsoft, I find there is still a lot of
confusion on how the different font types react (True Type, Clear Type,
etc).  Suffice it to say if a font is missing or not correctly working, surf
the internet.

 

 

SIDEBAR -

I also found a font which I use on parts of my QSL card designs (not part of
this inability to fit and need to resize fields issue) that I could
previously transfer from computer to computer, OS to OS would no longer
work. I was able to download it from the internet and all is well again.
While suffering this form field fit issue, I had not noticed until yesterday
that this font had disappeared and my call sign was not printing with its
unique font!  Just one more item to think about!

 

As always, I hope some find use in what I write!

 

Regards, Bill K1UQ

 

 

_______________________________________________
LOGic mailing list
LOGic at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/logic



More information about the LOGic mailing list