[Libreoffice-bugs] [Bug 126731] Editable pictures display as grey instead of colour in a LibreOffice Base form based on a read-only datasource

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=126731

Justin L <jluth at mail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
            Summary|Pictures display as grey    |Editable pictures display
                   |instead of colour in a      |as grey instead of colour
                   |LibreOffice Base form based |in a LibreOffice Base form
                   |on a read-only datasource   |based on a read-only
                   |                            |datasource
            Version|3.6.6.2 release             |3.6.0.4 release
         Resolution|---                         |NOTABUG
           Hardware|x86-64 (AMD64)              |All

--- Comment #27 from Justin L <jluth at mail.com> ---
Perhaps this isn't really a bug after all.
If you double-click on the image, you are not prompted to browse for a
replacement image. However, after the document is saved/exported, then you can
replace the image. Thus the image really is disabled on form open, and thus
should have some indication of that.

The form locks the image already in LO 3.5 - as far back as I can test.

OK - it has already been established that this is a read-only database.
Although the form is set to allow additional records etc, none of the controls
are active, and no part of the record is editable. So all data-entry parts of
the form are disabled, including the image.

(In reply to britfox42 from comment #8)
> - They appear greyed only when the "Read-only" parameter in the "General"
> tab of the "Image Control" form is set to "No".

(Nice bit of investigation.) That seems counter-intuitive doesn't it? Yet that
makes sense to me. If the picture is marked as read-only, then it has no need
of being disabled when the database does not allow editing.

So in summary:
-this only affects read-only databases or fields - since editing is disabled
-it only affects images that are marked as editable - while editing is
disabled.

It seems more and more clear to me that this is NOTABUG. And there is a logical
(if somewhat unintuitive) solution for the database designer.

P.S. The bibisect range was in LO 3.6.
P.P.S. Perhaps someone could complain that exporting as PDF shouldn't remove
the disable-highlighting, but who cares?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210119/52a4f446/attachment-0001.htm>