|Summary:||"Print Images" always greyed out when opening "Plugins" menu the first time|
|Product:||[Applications] kipiplugins||Reporter:||Wolfgang Bauer <wbauer>|
|Severity:||normal||CC:||devel, konrad.bucheli, nate, null, till2.schaefer|
|Latest Commit:||Version Fixed In:|
Description Wolfgang Bauer 2018-02-02 10:49:27 UTC
When you open the "Plugins" menu the first time (i.e. when the plugins will be loaded), the "Print Images" and "Print Assistant" plugins are always greyed out even if files are selected (and also stay disabled if you open the menu again). Changing the selection correctly enables/disables the menu entries accordingly though. But it should not be necessary to change the selection and open the menu again...
Comment 1 Till Schäfer 2018-08-04 09:59:25 UTC
I was able to reproduce this issue with Gwenview 18.04.3 on Gentoo. This also applies to the case on is not in the overview, but the image view. After the menu "plugins -> images" was opened, one needs to change the picture once to have the plugins enabled. Software: - kde apps: 18.04.3 (inkcluding gwenview and libkipi) - frameworks: 5.48.0 - plasma 5.13.3 - kipi plugins: 5.9.0
Comment 2 Peter Mühlenpfordt 2018-08-05 11:20:16 UTC
This seems to be a general issue. In digiKam these are the last two entries in the "Item" menu and they are also disabled until you select another image. The problem seems to be emiting the update signals for KIPI (currentAlbumChanged, selectionChanged) only before loading the plugins.
Comment 3 Peter Mühlenpfordt 2018-08-07 18:06:59 UTC
This was the commit where setEnabled() got lost on plugin init: https://cgit.kde.org/kipi-plugins.git/commit/?id=1fc7d86dbc94cb343b3c39b9dfda4d49a07f71e0 I'm not sure what the intention of this change was and if this should be fixed in the plugin code or in Gwenview (and maybe digiKam).
Comment 4 null 2018-08-07 22:16:37 UTC
Let's move this bug to kipi-plugins for now, since Gwenview has no special handling for specific plugins, and for other plugins it's working fine (why, though?). It might very well be an old problem which only surfaced due to 1fc7d86dbc94.