Am Montag 26 März 2007 23:17 schrieb Jason Keirstead:
> That is you should never be encrypting the message and then calling
> Kopete::Message::setBody with that, unless it is right before the wire
> transfer.
Thats the point. But I'm connecting to the signal
aboutToSend( Kopete::Message & )

That is where I encrypt the message. AFAIK this should be right before the 
wire transfer but also all other plugins connect to this signal and then 
Kopete decides what plugin comes first. How Olivier wrote, this is most 
likely in alphabetical order. Thats why gpg encrypted messages are logged in 
plaintext and otr encrypted ones are not.

>
> If you encrypt it before the wire transfer then that will break all the
> other plugin's processing. You should be encrypting only just before the
> message is actually sent over the wire, wherever that is in your code.
>
> The only reason the GPG plugin calls setBody is because it is a plugin
> and thus has no other option - the only reason the history plugin works
> with this is because it is processing the message before it. But this
> will never work in your case because you are the protool - you are
> always going to have first crack at the message.
>
Also kopete_otr is a plugin, not a protocol...

> > The only way I see to log the messages is to influence the order the
> > plugins are called but I havent found any way to do this so far.just
> > passes the messagetext to the libotr and returns the encrypted text.
>
> This has something to do with Kopete::MessageHandlerChain but I can't
> remember it's been too long :)
>

I will take a look this one...


Olivier Goffart wrote:
> >       ( Line 146 of otrplugin.cpp, in version 0.1: )
> >       msg.setBody( encBody, Kopete::Message::RichText );
>
> btw,  you should not use RichText here,   PlainText is better  (but it's not 
> the solution to your problem.)

Your right. changet to Plaintext now.


> _______________________________________________
> kopete-devel mailing list
> [email protected]
> https://mail.kde.org/mailman/listinfo/kopete-devel
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to