Summary: | display EXIF UserComment field in status bar or in full screen (diaporama) | ||
---|---|---|---|
Product: | [Applications] gwenview | Reporter: | Frédéric Bron <frederic.bron> |
Component: | general | Assignee: | Gwenview Bugs <gwenview-bugs-null> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | minterior, myriam, ufospoke |
Priority: | NOR | ||
Version First Reported In: | 4.11.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Frédéric Bron
2014-01-28 08:15:18 UTC
I want to link those related bugs with this one: Bug 110527, Bug 116164, Bug 110500 (In reply to comment #1) > I want to link those related bugs with this one: Bug 110527, Bug 116164, Bug > 110500 Do they depend on each other? Apparently not, so they should not be linked. It would be better to make one master report for the image data, and then make it depend on the resolution of the others. Sure, a master report that includes all those bugs would be better. I just wanted to link them in some manner because they all are related to comments and jpg metadata, although don't have dependencies a priori. PS. In Jira bugtracking system one can link issues indicating the relationship (duplicates, relates to, blocks or clones), but I didn't see a similar option here. There is an option, available for the product owner and people with appropriate rights, of course, but those do not either depend on each other nor do they block, so it makes no sense to link them through that option. Linking to a master bug makes more sense. Mind you: not all are really related, some are about displaying metadata, other about saving it, so those should not be linked anyway. Looks to me like more work to group them than actually implementing the feature.... Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. I do not see it being solved. However this is more a feature suggestion than a bug so it could maybe be closed. |