mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-23 06:00:41 -08:00
Update Android port
* doc/lispref/os.texi (Desktop Notifications): Revise documentation for android-notifications-notify to reflect changes. * java/org/gnu/emacs/EmacsDesktopNotification.java (display1): Convert notification importance to a legacy priority between Android 7.1 and 4.1. * java/org/gnu/emacs/EmacsPixmap.java (EmacsPixmap): Remove immutable bitmap constructor, as the underlying Android API functions are erroneously implemented. * src/android.c (android_init_emacs_pixmap): Cease searching for deleted constructor. (android_create_pixmap_from_bitmap_data): Create a pixmap, then fill it with the contents of the bitmap, in lieu of employing the aforementioned constructor. * src/androidselect.c (Fandroid_notifications_notify): Revise doc string.
This commit is contained in:
parent
947409d408
commit
df5a9a78b5
5 changed files with 129 additions and 116 deletions
|
|
@ -3220,15 +3220,25 @@ These have the same meaning as they do when used in calls to
|
|||
@code{notifications-notify}.
|
||||
|
||||
@item :urgency @var{urgency}
|
||||
The set of values for @var{urgency} is the same as with
|
||||
@code{notifications-notify}, but the urgency applies to all
|
||||
notifications displayed with the defined @var{group}, except under
|
||||
Android 7.1 and earlier.
|
||||
|
||||
@item :group @var{group}
|
||||
These two parameters are ignored under Android 7.1 and earlier
|
||||
versions of the system. The set of values for @var{urgency} is the
|
||||
same as with @code{notifications-notify}, but the urgency applies to
|
||||
all notifications displayed with the defined @var{group}.
|
||||
@var{group} is a string that designates a category to which the
|
||||
notification sent will belong. This category is reproduced within the
|
||||
system's notification settings menus, but is ignored under Android 7.1
|
||||
and earlier.
|
||||
|
||||
If @var{group} is nil or not present within @var{params}, it is
|
||||
replaced by the string @samp{"Desktop Notifications"}.
|
||||
|
||||
Callers should provide one stable combination of @var{urgency} and
|
||||
@var{group} for each kind of notification they send, given that the
|
||||
system may elect to disregard @var{urgency} if it does not match that
|
||||
of any notification previously delivered to @var{group}.
|
||||
|
||||
@item :icon @var{icon}
|
||||
This parameter controls the symbolic icon the notification will be
|
||||
displayed with. Its value is a string designating an icon within the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue