На 24.11.11 15:33, Bauersachs Ingo написа:
На 23.11.11 14:03, email@example.com написа:
I am not sure I understand this one. Could you please comment a bit?
The event PROACTIVE_NOTIFICATIONS of the notification manager is (only)
fired by the typing notifications. Therefore the rename from "proactive"
Any "Proactive Notification" is a typing notification received while
there were no windows open with the contact that generated it. So yes
you are right: PROACTIVE_NOTIFICATIONs are only generated by typing
notifications. That still keeps them different from regular typing
notifications that you get in the chat window during a conversation with
Before I translated the notification config UI, the plugin simply showed
the enum names (converted from Pascal-Casing to "Spaced-Casing").
I don't understand. Where was this happening? Is this related to your
change? In your example, what is the difference between Pascal-Casing to
the translation I simply took the same name as it was before because I
didn't knew better.
Maybe you remember that I told you I disabled the typing notifications,
but receive them despite the setting? Well, no wonder: The setting
behind the checkbox in Options->General->Message is not used anywhere.
OK. Just to be clear, this is not related to your string change, right?
IIRC, that setting was meant to prevent Jitsi from sending typing
notifications. It could have been broken along the way of course and if
so then we should have a look at it.