Bug 228314

Summary:	timeline view in digiKam scroll's left but not right
Product:	[Applications] digikam	Reporter:	gottkaiser <gottkaiser85>
Component:	Searches-TimeLine	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	anantapalani, caulier.gilles
Priority:	NOR
Version:	1.1.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:	2.6.0
Attachments:	Timeline view in digikam shown scrolled as far left as possible, and no images displayed.

Description gottkaiser 2010-02-24 14:34:03 UTC

Version:           1.1.0 (using 4.4.00 (KDE 4.4.0), MS Visual Studio 2008 SP1)
Compiler:          cl.exe
OS:                Microsoft Windows (i686) release 5.1 (XP Professional)

The "time-line" view in the program digiKam is broken.
When I scroll left it works fine but when I scroll right it doesn't work. - always using the mouse

One suggestion: Maybe it would be a good idea to give the arrow keys the ability to scroll as well.

Comment 1 caulier.gilles 2010-02-24 15:16:21 UTC

Not reproducible under linux

Probably it's relevant of digiKam kioslave

If it's true, all search tools must be broken

Gilles Caulier

Comment 2 Ananta Palani 2011-11-02 10:44:27 UTC

Created attachment 65153 [details]
Timeline view in digikam shown scrolled as far left as possible, and no images displayed.

It seems that the ability to scroll left and right in the timeline is now mostly restored. However, there is a problem where the scroll bar can not move past a certain point to the left (to the right it is fine), which is shown in the attached image.

Also, the image shows that when any of the dates are chosen, no items appear. Calendar, Search, and Map Search seem to work fine, so only Timeline appears broken on Windows.

Comment 3 caulier.gilles 2011-12-14 12:15:09 UTC

Ananta,

No image is displayed because no selection is done.

Try with current implementation from git/master, i changed date selection behavior.

Gilles Caulier

Comment 4 Ananta Palani 2012-02-03 12:27:31 UTC

This was fixed in 2.5.0, sorry I didn't respond sooner.