how should document-renames be handled in 4.1 branch?

[Milian Wolff]

Hey David,

can you tell me how I should fix https://bugs.kde.org/show_bug.cgi?id=204648 
(or do it yourself)?

I wonder what the right approach is, I could just remove the assert as it can 
be easily triggered with the steps provided. But I don't know whether it's 
correct.

The thing is: document get's savedAs, only the doc-url gets changed but the 
DUChain does not get notified. Hence next time we request the context for the 
old url, the same context gets returned (which is still open in the renamed 
document) and hence has a smartrange associated, just with a different doc/url.

Shouldn't maybe the SmartRange be updated in documentRenamed or similar? Btw: 
that signal doesn't seem to get emitted *anywhere*, which should probably be 
fixed as well...

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- 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/kdevelop-devel/attachments/20101204/0f27b72b/attachment.sig>