| *** zbenjamin_ is now known as zbenjamin | 01:06 | |
| *** nyov is now known as Guest63979 | 03:35 | |
| *** Ischwitch is now known as Ingvix | 04:39 | |
| *** Ischwitch is now known as Ingvix | 05:11 | |
| *** Ischwitch is now known as Ingvix | 05:40 | |
| *** Ischwitch is now known as Ingvix | 06:16 | |
| *** Ischwitch is now known as Ingvix | 06:51 | |
| tortoisedoc | yee update \o/ | 08:09 |
|---|---|---|
| tortoisedoc | I'd have a question on the notifications | 08:12 |
| tortoisedoc | havent been following lipstick in a while | 08:12 |
| tortoisedoc | https://git.sailfishos.org/mer-core/lipstick/commit/8a7fa617bb3d20c8f13c146ebfdcf8ae7d0944bc | 08:12 |
| tortoisedoc | there seems to be hints associated to notifications | 08:12 |
| tortoisedoc | any reference to documentation about them? | 08:12 |
| Nico[m] | You mean about hints in general or the sailfish extensions? | 08:13 |
| tortoisedoc | sailfish extensions I guess :) (the hints part that lipstick relies upon apparently in order to keep display on / off) | 08:14 |
| *** Ischwitch is now known as Ingvix | 08:15 | |
| Nico[m] | I'm confused now. Do you just want to keep the display on or do you want to do that with your notification? :D | 08:15 |
| tortoisedoc | so the notification I send, when it gets sent, turns the display black :) | 08:15 |
| tortoisedoc | how do I avoid that? | 08:15 |
| Nico[m] | Your notifications turn the screen off? How did you manage to do that? :D | 08:16 |
| tortoisedoc | oh it does? I had no idea :D | 08:16 |
| tortoisedoc | if you say so, it must be the case tho | 08:17 |
| Nico[m] | But if you just want to turn the screen on, when your notification arrives, you can just set the "x-nemo-display-on" hint, I guess | 08:17 |
| tortoisedoc | so I guess my notification is somehow missing a hint to tell lipstick not to turn the display off | 08:17 |
| tortoisedoc | ah there we go | 08:17 |
| tortoisedoc | so is there documentation about this somewhere? | 08:17 |
| *** Ischwitch is now known as Ingvix | 08:19 | |
| Nico[m] | Doesn't look like the hints are documented | 08:20 |
| tortoisedoc | thanks | 08:20 |
| tortoisedoc | so will dig in lipstick :) | 08:20 |
| Nico[m] | Why do you want to dig into lipstick for that? The name is descriptive enough :3 | 08:21 |
| Nico[m] | //! Nemo hint: Whether to turn the screen on when displaying preview | 08:22 |
| Nico[m] | static const char *HINT_DISPLAY_ON; | 08:22 |
| tortoisedoc | why, isnt it fun to dig around :D | 08:22 |
| pvuorela | don't rely too much on the undocumented ones, though. that one i could still consider removing. | 08:23 |
| Nico[m] | Fair | 08:23 |
| tortoisedoc | pvuorela : ah ok so there's a reason why its not documented yet :)( | 08:23 |
| Nico[m] | pvuorela: Well, worst case it just stops working, doesn't it? :3 | 08:24 |
| *** Ischwitch is now known as Ingvix | 08:24 | |
| pvuorela | Nico[m]: yes. | 08:24 |
| tortoisedoc | Nico[m] : forward compatibility FTW | 08:24 |
| pvuorela | the hint set is now a lot better what it used to be though, lots of things happened lately. | 08:24 |
| Nico[m] | In that case it should probably work for at least a year with the current update cycle, good enough! | 08:24 |
| tortoisedoc | @pvuorela because of that it would be even more interesting to better understand where the notifications are going | 08:25 |
| Nico[m] | I wish it was documented how to set custom led colors and such. The definition files for notifications are confusing. | 08:25 |
| pvuorela | the category files in general shouldn't be used if that's what you mean. | 08:26 |
| pvuorela | led is a difficult detail too as there's been color coding for different types of notifications and app developer choosing the color might break the expectation. | 08:27 |
| pvuorela | but in general there's been enhancements now, some new api, bad api removed. | 08:27 |
| pvuorela | or with bad, mostly meaning some old ad hoc hints. | 08:27 |
| tortoisedoc | I am wondering, my app didnt use to set any hints; so I guess in this case, the notifications by default assume screen has to be OFF? | 08:28 |
| *** Ischwitch is now known as Ingvix | 08:28 | |
| pvuorela | that sounded strange. no notification be even able to turn the screen off. | 08:28 |
| pvuorela | be -> should be | 08:29 |
| tortoisedoc | @pvuorela you'd amaze yourself wiht how many things can be done in SFOS :D | 08:29 |
| tortoisedoc | s/wiht/withg | 08:29 |
| *** Ischwitch is now known as Ingvix | 08:59 | |
| *** Ischwitch is now known as Ingvix | 09:06 | |
| *** Ischwitch is now known as Ingvix | 09:29 | |
| x2s | No update for me yet. How shall I brick my phone this way? I'm not impressed. ;) | 10:18 |
| mal | the release is in early access | 10:32 |
| x2s | ah, ok. The times I had to try everything from early access are over for me ;) | 10:33 |
| Nico[m] | But how are you going to brick your phone then? | 10:39 |
| x2s | That's a good question. I guess I have to use good ol' concrete. | 10:44 |
| abranson | I think we need to stress the testing element of early access a bit more. too many people are getting into it without realizing that it could cause problems. | 11:14 |
| Nico[m] | Yeah, I always take backups and make sure if my phone dies, that it is not that bad, if I can try fixing it in the next week, but I don't think everyone is that careful :D | 11:17 |
| *** frinring_ is now known as frinring | 11:58 | |
| ol | <x2s "That's a good question. I guess "> Sorry man, I have no concrete for you. | 14:57 |
| x2s | ol: Clay could work, too. ;) | 15:21 |
| kirvesAxe | Is there a list somewhere on feature phones that have been tested compatible with Sailfish? | 16:06 |
| attah | kirvesAxe: https://together.jolla.com/question/136143/wiki-available-devices-plus-rumored-and-legacy-devices-running-sailfish-os/ | 16:40 |
| kirvesAxe | attah, thanks. I was mostly interested to see if those retro-nokias would have any hope of getting a sailfish.... seems like not much. | 16:56 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!