Summary: | previous and next image is showing weird results | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Alexandre Racine <alexandreracine> |
Component: | ImageEditor-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, marcel.wiesweg |
Priority: | NOR | ||
Version: | 0.10.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Attachments: |
capture-A
capture-B |
Description
Alexandre Racine
2009-05-04 05:50:13 UTC
Created attachment 33335 [details]
capture-A
Created attachment 33336 [details]
capture-B
Never see this dysfunction on my computers sound like a cache problem... How many ram do you have ? gilles caulier Maybe a missing call to viewport()->update() together with Qt redrawing very conservatively? What is your Qt version? Your graphics driver? Gilles : 4GB RAM, video card is a GeForce 8800 GT with 512MB RAM. Marcel : qtconfig tells me 4.5.0 and nvidia driver 180.44. Additional note : I have been using it for a while now and tt only does this when going to the first picture or when going to the last picture. This would confirm that it is not a memory bug. Additional stuff : On my comment above. It mostly do so with the first and last picture, but it did it on some occasion with other pictures. Nevertheless, I have found a way to make this bug happen more frequently. Look at a picture, open a pannel, let's say the meta-data one, and clic on the arrow right, right, right a couple of times and sometime the next picture does not load. Clicking anywhere will make it visible correctly. Alexandre, Can you check again using digiKam 1.0.0-beta1 ? Gilles Caulier It seems ok, but I am testing this with another machine. If 1.0 makes it to the next ubuntu 9.10 official and this is still here, I'll reopen. |