The user can't resize the Meta/Semantic Info panels, or hide each. http://i.imgur.com/cPa24Bl.png Gwenview-4.12.2 or 4.12.3, who knows? http://i.imgur.com/piq2vv7.png The ebuild is for 4.12.3. Reproducible: Always Expected Results: Panels should be resizable by the user.
I would propose merging the two panes. Meta and Semantic are almost synonyms, at least in the context of image Meta/Semantic data.
Yes that sounds good.
Metadata are the photo (camera) Exif data. Semantic Information is related to the semantic desktop, information that the user adds. I think it would be a bad idea to combine both fields. To me they are not related and would not good if the semantic information is confused with the Exif data embedded in the photo from the camera. On the other hand, it would be good to be able to choose which field should be shown and be able to resize them. Particularly I hate the semantic desktop and everything related to file and activities indexing. Is very helpful to me can see all Exif data in Gwenview lateral panel, but the semantic information field covers half of the panel and is very annoying. I vote to be able to hide the semantic information field.
Metadata and semantic information are indeed two different items, and as such should be separated. A splitter between the two at the very least would seem sensible, allowing users to allocate area in the panel according to their preference. Ideally the display of semantic information (and indeed metadata) should be optional. The display of either, or both being a user set option. Regards, Paul
An option to hide the semantic information would help. Today the meta information is unusable for me because I have to scroll on each picture.
"Semantic" metadata only needs to added by the user because the camera and/or the computer was too stupid to add that metadata in the first place.
Three months just to put the string next to the label and to make a frame resizable and no progress yet...
(In reply to comment #7) > Three months just to put the string next to the label and to make a frame > resizable and no progress yet... My dear Doctor, the link to add the patch that you find so easy is just below the Add Comment button. Talk - Action = 0.
My dear Alan, what a pity I'm unfamiliar with the Gwenview codebase and all my time is spent contributing elsewhere.
Still valid for 4.14.0 (that version is not available in the "version" combobox).
I confirm that we still can't resize/hide the semantic panel in Gwenview 4.14.0 I think we can al least mark this as confirmed, to give it more visibility. Thanks.
*** This bug has been confirmed by popular vote. ***
*** Bug 363391 has been marked as a duplicate of this bug. ***
Semantic information has ratings and comments, which are important, so we can't hide that section entirely. But yeah, that comments box is huge. We could definitely allow you to resize the separator, or just make the comments box much smaller. If you don't like either, you can always switch to a different tab (the tab box is on the bottom of the view). I'll see if I can whip up a patch at some point soon.
*** Bug 259141 has been marked as a duplicate of this bug. ***
(In reply to Nate Graham from comment #14) > If you don't like either, you can always switch to a different tab (the tab > box is on the bottom of the view). Not really, as (personally) I need to see the meta information. (As opposed to the semantic data, which I don't use.) > I'll see if I can whip up a patch at some point soon. A splitter and ability to resize would be great. Thanks.
Yeah, I'll see about a splitter, and making Semantic info smaller by default.
Longer-term, a better layout would be implemented with https://bugs.kde.org/show_bug.cgi?id=196017 Short-term, we can still do this.
This is still the most annoying non feature on gwenview. In my case (I guess most photographers and so) doesn't use the oversized semantic box in the panel, and if you want more metadata seen on the screen you have to scroll each time to find what you need. I would really see a option (it can be in config file) to disable completely this panel. seen on 18.08.3
(In reply to Nate Graham from comment #17) > Yeah, I'll see about a splitter, and making Semantic info smaller by default. Has this been kicked into the long grass? A short-term fix would be really appreciated :)
No, there are just a lot of other competing priorities. :) Would you like to have a go yourself? We have great documentation! https://community.kde.org/Get_Involved/development
I'm guessing it would probably be a fairly trivial patch. If I already had a development environment set up, and some prior experience, yes I would willingly have a go. Alas, that is not the case, and, as you said, "there are just a lot of other competing priorities."
Git commit 26b39137a93c9fc368d2bf8962d6a98dfd24077f by Nate Graham, on behalf of Corbin Schwimmbeck. Committed on 21/10/2022 at 19:29. Pushed by ngraham into branch 'master'. Add a splitter to the information sidebar In Gwenview, the information page of the sidebar consists of two halves: an upper section displaying varying amounts of image details, and a lower section displaying a rating, tags, and description. Due to the expanding nature of the description's plain text edit, it takes up half of the sidebar by default, and is usually completely empty. This additional space could be better used to show more image details, as requested in this bug report: So, I have added a splitter, allowing you to move the previously-static central divider, and made sure that Gwenview remembers its position between sessions. By default, the appearance of the sidebar looks identical to how it did before this patch. Below are two screenshots, one of the splitter moved to its highest, and another at its lowest position.   M +54 -3 app/mainwindow.cpp M +3 -0 lib/gwenviewconfig.kcfg https://invent.kde.org/graphics/gwenview/commit/26b39137a93c9fc368d2bf8962d6a98dfd24077f
*** Bug 459478 has been marked as a duplicate of this bug. ***
@Corbin Schwimmbeck Many thanks, appreciate your effort :) @Nate The screenshot URIs in comment 23 need repairing.
(In reply to Paul from comment #25) I'm a new contributor, and this was within my capabilities, so I figured this was a good place to start. I'm glad so many people can benefit from this. I'll be looking into more bugs soon :)
That would be wonderful!