Created attachment 123070 [details] Not scrolling to the album pictures ! SUMMARY From the tree view (left part) Clicking on a parent Album folder scroll the main view (central part) in a strange place. STEPS TO REPRODUCE 1. Click on a parent Album folder with pictures at the root and pictures in the child folders/albums. 2. 3. OBSERVED RESULT The main view (central part) scrolls to a strange place : - not on the parent album picture (my preference) - not the beginning of the child Album - not on the last child album EXPECTED RESULT The main view (central part) should scroll to the root album we clicked on , showing directly attached pictures. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION See attached example.
Created attachment 123071 [details] Expected behaviour (scrolling to the clicked Album).
This is a desired behavior and was so wanted by the users. I just tested it here. The view scrolls to the last selected item to make it visible. After starting the program, the view has the desired position. Mark an item deeper in the view. If they return to view, the view will scroll to that item. Maik
Hello Maik, i understand the idea, although it may be critizable : when i dispatch pictures from a root album to child albums, i do not need to jump to destination albums each time. This slows down the production workflow, as i need to go back to my source album each time, scrolling and scrolling up. Anyway, even if a unselect the picture located in a child album , and then click on the parent album, it DOES NOT bring me up to this upper level. On the contrary, it reselect automatically the previous picture, and sticks me in the child album. This is annoying : it means i can't navigate to the parent album using the Treeview (while it works like a charm on child albums). Let me send you a video of my navigation experience issue...
I think we do not need a video here. The current behavior is not a bug, but is already present for years and I think so synonymous of most users so demanded. We often have bug reports when the view is not at the position of the item left in the editor. Everyone has a different way of working, and I would not like it if the view is always back to the beginning. Maik
Hi Alexandre, I second Maik here. We receive many report to implement this functionality in the past. So the current behavior is not a bug but a real feature. Best Gilles Caulier
Ok. then what is the procedure to jump and show the pictures located in the root of a parent album ? Alex
Hello Maik, Gilles, Digikam targeted behaviour is great : Digikam goes back "at the position of the item left in the editor", and this is indeed very useful. Thank you for that appreacited feature. My case is different : once I'm finished editing in a sub-folder, if I want to navigate to the parent album/folder, sometimes it works, sometimes it does NOT. The behaviour is unstable, and this is the reason of my bug report. I've made 10x attempts this morning, each time restarting Digikam and simply opening the "Editor" in a sub-child album/folder. - 80% of the tentatives, Digikam TreeView navigation works perfectly : when I click on the parent folder/Album, thumbnail view scrolls up and shows me the pictures directly stored in this parent Album. GREAT, that's what we expect ! - 20% of the time it does not have the same behaviour : thumbnail view stays locked to a child folder/album. While the TreeView browser DOES highlight the parent Album. + This happens even if all images in the child album have been UN-selected. + I have made a video of this, but unfortunately the sound was not recorded. I need to re-do it or add an off-line commentary ... + I've found a workaround : when the strange Navigation occur, I just need to restart Digikam.
Hello again, Today I worked as usual, no TreeView / scrolling bug... and then, suddenly, the bug came back. This time I was able to record a short video (2 min), with my comments. You can find it here : https://1drv.ms/v/s!Ahp2yXCYf8WmihdpZkgx1VF4FGAL?e=sWH4Bb please can you watch it and give me your feedback ?
Created attachment 123168 [details] debugview traces during the scrolling bug + attached debugview traces in case it can help.
I understand what you mean, but it's not a bug. digiKam has an album history, this also remembers the selected items. If you activate the view of sub-albums, you have to understand the icon view from album as "one" album. You can also disable the view of album categories, then you will not be able to see in which sub-album you are currently active. So if you select an item deeper in the icon view, it scrolls beyond the boundaries of the sub-albums. Maik
ok, Thank you Maik. in the next release, can we make this behaviour configurable, with a global parameter in the treeview options ? Thanks to that option ("file explorer mode"?), digikam treeview will be able to rapidly scroll-up to the parent pictures if i click on the corresponding parent "folder" in the treeview. Exactly like navigation in a classical "file explorer" in fact. Best regards
So why do not you just disable the view of sub-albums? A classical file explorer does not show in its file view also the files of the subdirectories, only the selected directory. Maik
OK, I will try this setting. (I do agree that the flattened view is better/nicer... it's just that I want to be able to reach easily parent album content, in case there are still some pictures in it). Alex
Hello, Where can I find this setting ? I've looked there without success : - Options/Views/treeview - Misc/Behaviour/Scroll current item to the center of thumb bar has no consequence on my issue/ thanks
disable Menu-> View-> [x] Include Album Sub-Tree Maik
Thanks Maik, found. Before closing the ticket, please can you confirm me that when the checkbox is ticked, the thumbnail view is supposed to come back "at the position of the item left in the editor" ? (which is OK to me) the manual is not clear about that, it just says : https://docs.kde.org/trunk5/en/extragear-graphics/digikam/menu-descriptions.html " View → Include Album Sub-Tree If a hierarchical album structure exists, the currently selected branch will be displayed in full depth."
Yes, this is the expected behavior... Gilles Caulier