Recently used tags pop up window

[Andrew Goodbody]

On 14/09/2025 19:29, Maik Qualmann wrote:
> Which recently used tag menu are you referring to exactly? In the right-click
> context menu, under "Assign Tag"?

No, I was not aware or had forgotten about that method. I can at least 
use it as a workaround as it does work.
I am talking about the button towards the bottom right of the right hand 
tags sidebar, just to the right of the 'Tags already assigned' button 
which itself is to the right of the 'Search...' box. See the attached 
screenshot showing this button clicked and highlighted but the pop up is 
not visible.

> There's currently an issue with Qt6 and QMenu popups under Wyland and for some
> Windows users.
> I can't reproduce the QMenu issue here either under openSUSE Tumbleweed with
> Wyland or with any of my Windows installations. I also don't see that we're
> using QMenu incorrectly in the code. Can you reproduce this bugs as well?
> 
> https://bugs.kde.org/show_bug.cgi?id=505103
> https://bugs.kde.org/show_bug.cgi?id=501862

No, I cannot reproduce those bugs, they seem to produce the correct 
behaviour for me.

Andrew

> Maik
> 
> Am Sonntag, 14. September 2025, 17:13:35 Mitteleuropäische Sommerzeit schrieb
> Andrew Goodbody:
>> Hi,
>>
>> I have built digikam with source pulled today. I am on Debian 13.1 and
>> build with QT6. All optional libraries are present apart from libjpeg > 8.0.
>>
>> If I click on the button to open the recently used tags list while the
>> scan for new items is still running then it will generally open as
>> expected. If I select a tag each time and apply it then I may be able to
>> repeat this as many as 4 or 5 times, but sometimes it will not open at
>> all or I may only get 1 go at it. If I wait until the new items scan
>> finishes then it will never work. If I do not select a tag but just
>> click away then it will never open again. If I do not apply the change
>> then it will not open again. When it does not work the button is
>> highlighted until I click it or somewhere else again. Clicking the
>> button does not generate any messages in the debug log, at least in the
>> non-functioning state. It is hard to see if any messages appear when it
>> does work as the new image scan is running and generating many of its
>> own messages.
>>
>> Can anyone else see this behaviour?
>>
>> Thanks,
>> Andrew
> 
> 
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RecentlyUsedFail.png
Type: image/png
Size: 155143 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20250915/2f2ddc35/attachment-0001.png>