I'm not sure about where the warning should be showed but the method is marked as deprecated in a same way as the old constructor is.

Dne 25. 4. 2018 12:56 napsal uživatel Dave Mielke <[email protected]>:

[quoted lines by Robert Pösel on 2018/04/25 at 09:57 +0200]

>call to: notificationBuilder.setPriority(Notification.PRIORITY_LOW)
>is deprecated too, so it should be used only in the else branch with
>old constructor, because with new API is priority determined by the
>notification channel's importance value.

Does it actually cause a warning? I left it that way because, from a coding
point of view, it's just the safer way to do it. It's easy enough to change, of
course, but, to me, calling it just in case still seems reasonable.

--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke           | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: [email protected] | Ottawa, Ontario   | Twitter: @Dave_Mielke
Phone: 1-613-726-0014 | Canada  K2A 1H7   |


_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Reply via email to