<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
I am pleased that others still are struggling with the windows
problem.<br>
unfortunately still no one seems to really want to take the actual<br>
problem.<br>
it was certainly a lot of windows user gratifying when digikam
even<br>
with large collections of images would work perfectly. with small<br>
pictures collections usually no one needs special management.<br>
I hope soon of a workable solution to the reuse of under windows<br>
digkam heard.<br>
<br>
wolfgang<br>
<br>
Am 06.12.2012 19:41, schrieb Brian Morrison:<br>
<span style="white-space: pre;">> On Thu, 06 Dec 2012 18:14:11
+0000<br>
> Andrew Goodbody wrote:<br>
><br>
>> On 05/12/12 16:52, Brian Morrison wrote:<br>
>>> On Tue, 04 Dec 2012 20:59:53 +0000<br>
>>> Andrew Goodbody wrote:<br>
>>><br>
>>>> If you want to build digiKam from source, I can
probably tell you<br>
>>>> the place to increase the time out.<br>
>>><br>
>>> That might not be the correct way to fix it, the
problem is more<br>
>>> likely to be that the KDE libraries for Windows are
not as stable<br>
>>> as those on *nix because they are less developed
and there isn't<br>
>>> the effort available to improve the port.<br>
>><br>
>> No, it is not the correct way to fix it or I would have
sent a patch <br>
>> years ago. Yes literally 2 years ago. It is however a
pragmatic way<br>
>> to get it to work right now. I know it will make it
work as I tried<br>
>> it out back in 2010. My bug report will be 3 years old
in January and<br>
>> there has been no movement on it since. Laurent said it
was a big<br>
>> issue for him and Wolfgang would also like a fix and
there must be<br>
>> many others not even on this list. I will not hold my
breath while<br>
>> waiting for someone to fix it the correct way.<br>
>><br>
>> You can say 'not our problem' as much as you like but
the fact is<br>
>> that this bug is our problem as digiKam seems to be the
only<br>
>> application to be badly affected by it. It is
negatively affecting<br>
>> the users of digiKam on Windows and therefore harming
the reputation<br>
>> of digiKam as a whole.<br>
><br>
> Of course it is "our" problem, for some value of our. I'd
like to see<br>
> digiKam work well on Windows too, but I have no way of
fixing it myself<br>
> as I don't know the code at all. The question is, what is
digiKam doing<br>
> differently from other KDE programs ported to Windows and
is the<br>
> resulting problem something that needs fixing in the KDE
ported<br>
> libraries or can it be fixed in digiKam itself? Until the
exact reasons<br>
> are understood and a path to getting it fixed established
then no one<br>
> seems to know what to do.<br>
><br>
> I shall copy this to Ananta and see if he has anything to
add, he knows<br>
> more than I do about this.<br>
></span><br>
<br>
</body>
</html>