Re: API-CHANGE - dropping string properties which use vnd.sun.star.GraphicObject URL

Howdy,

Not at all sure this was from anything your work did, but to give you a
heads up;

Working with the latest daily build (may 4th) under Ubuntu 18.10 (64bit).

Entered an issue today
https://bugs.documentfoundation.org/show_bug.cgi?id=117435

The issue includes two test ODB files, almost identical. Single table, form
with image control, report (RB) with image control and 3 test images.

File one stores the images in the embedded database. File two stores a URL
to external image files.

File one (Image binary in table) works as expected under 6.1 for both the
form and report. However It fails to display any image data after migration
to a Firebird data engine.

File two (URL in table)  works as expected before and after the migration
to Firebird.

So, as I said thought I would just let you know.

Best wishes, Drew


On Sat, Apr 28, 2018 at 8:01 PM, Tomaž Vajngerl <quikee@gmail.com> wrote:

> Hi,
>
> On Sat, Apr 28, 2018 at 10:34 AM, Drew Jensen
> <drewjensen.inbox@gmail.com> wrote:
> > Howdy list,
> >
> > Reading over this, and sorry if this is a naive question, but I was
> > wondering if this could effect the way image controls work in forms and
> > reports.
> >
> > When an imagecontrol on a form (or Report Builder report) is linked to a
> > character field in a data table the control reads a URL from the data
> field
> > and loads the image into the control as the user moves through the table
> or
> > as a report is generated.
> >
> > For a Form, the user can also insert a graphic into the control via the
> GUI
> > and table column with the URL.
> >
> > Like I say I don't have enough detail knowledge of how this works, under
> the
> > hood, to know if what is changing here could be an issue or not, so
> thought
> > I would ask.
> >
> > Thank you for your time in advance.
>
> Yes, it does effect the image controls but just in the way that you
> can't use the internal URL with the scheme
> vnd.sun.star.GraphicObject:<ID>. In that case you will need to load
> the image first with XGraphicProvider and set the "Graphic" property
> instead of the "ImageURL" property.
>
> It would be good to try this use cases out with the Report Builder
> with the current master.
>
> Regards, Tomaž