New Blog Post: PDF/A and Metadata

Rich Text output when running on a Mac (WINE via Crossover)

edited February 2017 in Devices
RD 17.03 (still not installed 18 yet, but I suspect this issue would be
in v18 too )

Not sure if this is supported but it's the only problem we've found to
date with running our app and RB on Macs: The TppRichText component
doesn't render anything when previewed or exported to PDF. At first we
thought it might be a font issue or the RTF meta/markup data being
different if created via the WINE RichEd20.dll, but if a report with RTF
is created on a Mac and then run under Windows it renders fine.
Furthermore, we are also using the "TRichView" addon for RB and this
DOES work properly. Finally, if we set the RichText memo to "stretch" we
can tell that is 0x0 pixels, suggesting it thinks it has no text.

Any chance this could be investigated? It's the only barrier to signing
off our app as being able to run on a Mac without a Windows desktop.

Thanks.

Comments

  • edited February 2017
    Hi Paul,

    We do not actively support using ReportBuilder with WINE.

    We have not heard of this before but my first thought is that if it
    functions with Windows but not with WINE, it is likely a WINE issue
    (either with the RichText .dll or other translated library).

    1. Are you able to see the Richtext in the preview?

    2. In RB, all Richtext is converted to metafiles before
    displayed/printed/exported. This is done inside the
    TppRichTextDrawCommand.AsMetaFile routine. You could trace into this
    routine and see if a valid metafile is being created.

    You will notice a commented out line of code near the bottom we use to
    debug this routine that saves the metafile to file. You could use this
    (with a different path) to test.


    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited February 2017
    On 09/02/2017 15:56, Nico Cizik (Digital Metaphors) wrote:

    Nothing at all.


    ah, that's a good starting point. I'll work with that, thanks.
This discussion has been closed.