Bug 180953 - clicking a folder closes or open it instead of just view it
Summary: clicking a folder closes or open it instead of just view it
Status: RESOLVED INTENTIONAL
Alias: None
Product: digikam
Classification: Applications
Component: Albums-MainView (show other bugs)
Version: 0.10.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-16 11:30 UTC by Nadav Kavalerchik
Modified: 2012-06-27 11:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.10.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nadav Kavalerchik 2009-01-16 11:30:59 UTC
Version:           0.10.0-beta7 (using 4.1.86 (KDE 4.1.86 (KDE 4.2 >= 20081221)), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.26-1-amd64

clicking on the "+" or "-" should expand or hide the sub-folders under that (clicked) folder.

currently, this behavior is happening if i click the folder itself.
it should just display the images in that folder and not hide or display the sub-folders in the tree.
Comment 1 caulier.gilles 2009-01-16 15:42:22 UTC
Andi,

You haven't fixed something in folder-view mouse click behaviors recently ?

Gilles
Comment 2 Andi Clemens 2009-01-16 17:42:20 UTC
No,

isn't this the standard behavior now? Clicking on folder name or icon should expand / collapse the tree?

Andi
Comment 3 Marcel Wiesweg 2009-01-16 17:58:18 UTC
Yes this is intended behavior.
With a recent fix expand/hide does not happen when the new folder was not previously selected, so you can go to the parent folder without hiding the tree.
Dont know if this fix was in beta7 already.
Other than that, suggest WONTFIX here.
Comment 4 Nadav Kavalerchik 2009-01-16 20:42:05 UTC
clicking on the little "+" or "-" is suppose to expand or hide the sub folders
BUT, the thing is... that clicking the folder's name does this.
and i do not think it should be the intendant behavior
Comment 5 Marcel Wiesweg 2009-01-17 14:24:24 UTC
Long discussion is at bug #126871.
For us this is intentionally implemented, so not strictly a bug. Discussion is at the place named above.