| *** ChanServ sets mode: +v T4 | 02:10 | |
| *** ChanServ sets mode: +v T4 | 08:02 | |
| T4 | <neochapay> https://github.com/nemomobile-ux/glacier-contacts/commit/f20b43c57344273dd8a1c2b34428a42cf622abd2 | 11:19 |
|---|---|---|
| T4 | <neochapay> https://github.com/nemomobile-ux/glacier-messages/commit/7f0e7d9610f3dce30c5b00a0e0991ed679988a0f | 11:20 |
| T4 | <neochapay> Now we can open conversiation from contracts application | 11:20 |
| T4 | <locusf> wow nice ! | 11:20 |
| T4 | <neochapay> But not understand how call messages application from notify | 11:20 |
| T4 | <eekkelund> 👌 @neochapay | 11:20 |
| r0kk3rz | is the notification handling standard lipstick? or do we have our own compared to silica | 11:21 |
| T4 | <neochapay> i don't know about standart lipstick :)))) | 11:22 |
| T4 | <neochapay> r0kk3rz if you fix it i will be happy :)))) | 11:22 |
| r0kk3rz | i know how it works in sailfish, but i might have to poke and see how it works in nemo | 11:24 |
| coderus | https://sailfishos.org/develop/docs/nemo-qml-plugin-notifications/qml-nemo-notifications-notification.html/#remoteActions-prop | 11:25 |
| coderus | it should be handled in lipstick indeed. | 11:25 |
| coderus | https://git.merproject.org/mer-core/lipstick/blob/master/src/notifications/notificationmanager.cpp#L1092 | 11:26 |
| coderus | seems it "just works" | 11:26 |
| T4 | <locusf> voodoo magic man | 11:27 |
| T4 | <locusf> lipstick-tools should help | 11:29 |
| T4 | <locusf> voicecall-qt5 needed something special for notification handling | 11:31 |
| T4 | <locusf> it was something to do with being the only adapter for a certain dbus queue | 11:33 |
| T4 | <locusf> so no two dialers should exist | 11:33 |
| T4 | <locusf> not sure | 11:33 |
| *** ChanServ sets mode: +v T4 | 14:08 | |
| *** ChanServ sets mode: +v T4 | 20:54 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!