serious kfiledialog bug

[Matthew Woehlke]

Rafael Fernández López wrote:
> I can undestand now bug #176657. The attached patch fixes the problem.

I guess that means the answer to 'is this known' is "sort-of" :-). Glad 
I could help.

> Basically what's going on is that KDirOperator doesn't know the context. It 
> will emit that the file has been selected without knowing whether you are 
> saving or loading.
> 
> This means that you always load or save with one or two clicks. You cannot 
> load with one click, and save with two. KDirOperator doesn't get that far (at 
> least until now).
> 
> At the same time KFileWidget only receives from KDirOperator the fileSelected() 
> signal, without the context of what happened: one or two clicks on it (it 
> could filter by using operationMode attribute...).

Ok, I admit. You totally lost me :-).

> OK to commit ?

I hope someone else can answer that, because given the above, I'm afraid 
to even attempt to understand the code ;-).

I won't have time to test this patch now, and probably won't get to it 
over the weekend. Let me know if you still want me to test Monday night.

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
For great justice!! -- Captain (Zero Wing)