| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| | |
Approved by Gustavo Pichorim Boiko, PS Jenkins bot.
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
This can happen if noone outside of MessagingMenuApp holds a reference to the
message and somebody calls remove_message() with a pointer they got from
_get_message() (which doesn't return a ref).
messaging_menu_app_remove_message_by_id() really wants a valid 'id' pointer
during its lifetime.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
And add parameters 'action' and 'parameter' (though they are not set yet).
|
| |
|
|
|
|
|
|
| |
Right now, this is only used to clean up internal data structures in
libmessaging-menu. It's not exposed to the application itself.
|
| |
|
|
|
|
|
| |
This is not exposed in the indicator menu yet.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the protocol was simply a menu model and an action group of the
currently active sources. The service inserted the menu as a section into the
indicator menu.
This doesn't work anymore, because applications can (soon) expose individual
messages, and the messaging menu doesn't always display all of those at once.
This patch introduces a more specific d-bus API.
That API is still considered private: applications have to use
libmessaging-menu.
|
|
|
|
|
|
|
|
|
| |
Adds MessagingMenuMessage, which allows adding individual messages with titles
and body previews to the messaging menu with messaging_menu_app_append_message.
This only adds the new API, messages are not actually sent to the messaging
menu yet.
|
|
|
|
|
|
|
|
|
| |
MessagingMenuMessage allows adding individual messages with titles and body
previews to the messaging menu with messaging_menu_app_append_message.
This only adds the new API, messages are not actually sent to the messaging
menu yet.
|
|
|