Devicetype ReportTextFile

edited February 2015 in Devices
Hi,
I recently moved from D2010 with RBuilder 12.01 to
XE7 RBuilder 16.

I have a problem using Devicetype := 'ReportTextFile' in XE7. Some fields
are cut off or shifted by usually a character. This data after is exported
it is then parsed and structured.
Obviously this is a big problem and can't go back and adjust each template
especially once made by customers.
So how can we fix this quick?
Than you

Comments

  • edited February 2015
    Hi Eug,

    Do you have an example report that exports correctly with RB 12 and
    incorrectly with RB 16? If so, please send this report to us in .zip
    format and we'll track down what could be causing the problem.

    Send the example to support@digital-metaphors.com.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited February 2015


    Sample sent.
  • edited February 2015
    Nico, I got the the ppFileDev.pas you sent me but unfortunately there is no
    change in the output.
  • edited February 2015
    Based on my findings version 12
    function GetNearestCourierSize(aFont: TFont) returns 8
    while version 16 returns 10
    Is it because of the bitmap.canvas vs Printer.canvas?
  • edited February 2015
    Based on my findings version 12
    function GetNearestCourierSize(aFont: TFont) returns 8
    while version 16 returns 10
    Is it because of the bitmap.canvas vs Printer.canvas?

    More findings:

    If I force the result of GetNearestCourierSize to 8
    and use CalcCharacterGrid from version 12
    everything lines up perfectly but changing the Rbuilder source is not an
    option.
    I thought I would share what I found and wait for your response.
  • edited February 2015
    For anyone following this thread, there is a new patch available for RB
    16.01 that solves the text truncations issues. Contact
    support@digital-metaphors.com to receive the patch.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.