[rkward-devel] windows quirks

[Thomas Friedrichsmeier]

Hi!

Thanks for your testing, so far. I'm still quite confused, on what might be 
the problem. But if nothing else, your results seem to narrow down the problem 
to the user's own home directory. One more idea for testing in this direction:

- cd to c:\ before starting RKWard
- in RKWard setwd ("C:/Documents and Settings/username")
- then open the file dialog

If that does *not* trigger the crash, then at least that translates into a way 
for us to work around the bug.

Also, could you describe the crash itself, in more detail? Do you get an 
application has crashed message? Or does rkward simply become unresponsive? 
Immediately after calling File->Open, or with some delay?

I'm also still trying to understand, what might be special about your setup 
for this to occur. On the WinXP boxes that I have tested so far, I have not 
seen this problem. Are there many drive letters on your system? Network or 
special drives? Are all drive letters accessible? Could you post a screenshot 
of a file-dialog pointed at your home directory?

On Wednesday 21 November 2012, Enguerrand de Rochefort wrote:
> By the way, even if the application does not crash, the file browsing
> dialog takes a long time to come up.
> (almost one minute)

Hm, it's normal for the file dialog to take a while, particularly for the 
first file dialog you open. Almost one minute sounds *very* long, though. Is 
the hard-disk working during that time? If you start up the process manager, 
does rkward.frontend.exe hog the CPU while the file dialog is starting? How 
long does it take the dialog to open the second time?

Thanks!
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20121121/f58bcfe7/attachment.sig>