import emoticon broken in kopete when importing to the default emoticons

[Roderick B. Greening]

Binary package hint: kopete

In at least 7.10 and up to the latest 8.04 (alpha/beta) release of Kubuntu, kopete does not allow you to import emoticons when on the default emoticon set. You should either a) be able to edit the Default and have the changes in your personal .kde/share or b) it should appear greyed out and be documented that editing a default emoticon set is not possible - install one.

Obviously a) is preferable. Right now, the Default emoticon set is installed system wide and the import option exists but does nothing. This import feature can use some additional testing and polishing to ensure all facits of the feature are working correctly, which today, they do not appear to be (unless I have missed something).

e.g.) when deleting an emoticon, it does not remove the old image. It should ask for confirmation to remove the image, rather than leave it there.

[Roderick B. Greening (roderick-greening)]

This appears to be pieces from this patch/source: http://www.kde-look.org/content/show.php?content=54968&forumpage=4&PHPSESSID=cae

I believe if this code were enhanced, and the patch re-applied, we would get a better experience.

[Roderick B. Greening (roderick-greening)]

Looking at the patch, this line may be one of the culprits causing an issue:

"KIO::copy( d->activeElement.getAttribute("src").string(), xmldirname);"

If Default does not yet exist in the users private share directory, it creates a file called default rather than copying the emote to the Default directory in the users private share.

Also, if you manually create the directory, and then do an import, you can get it to appear in this directory, but it's still not correct and then Default will show up as a theme twice in kopete.

[Jonathan Thomas (echidnaman)]

Wrong bug, my bad.

[Jonathan Thomas (echidnaman)]

Is this still an issue in Intrepid?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!