I reproduced the bug. Unfortunately, it won't be easy to fix.
I'll shortly tell what's happening:
1. create 2 tabs and open 2 slow remote connection in them (dir listing
is slow)
2. on tab1 refresh (Ctrl+R)
3. on tab2 refresh paralelly (tab1 is refreshing)!!! (Ctrl+R)
What's happening?
- Tab1:
qApp->processEvents() is called and waiting to finish
- Tab2:
inside the Tab1 cycle another qApp->processEvents() is called
I think, that Krusader don't really like embedded qApp->processEvents()
calls.
My personal suggestion is to make a hard work before 1.80 and REMOVE ALL
qApp->processEvents() calls. That will drastically increase the
stability of Krusader.
I think, that 90% of the Krusader crashes are caused by calling
qApp->processEvents().
Rafal, Fathi:
-----------------------------------
Avoiding the crash: please don't do anything with krusader, while a tab
is refreshing. Wait the end of the refresh, and after that it's safe to
work. Before 1.80 we will find a solution to the problem.
Thanks,
Csaba
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
