Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

desktop::notify::notification(3pm) [debian man page]

Desktop::Notify::Notification(3pm)			User Contributed Perl Documentation			Desktop::Notify::Notification(3pm)

NAME
Desktop::Notify::Notification - a notification object for the desktop notifications framework VERSION
Version 0.03 SYNOPSIS
# $notify is an existing Desktop::Notify object my $note = $notify->create(summary => 'Rebuilding FooBar', body => 'Progress: 10%'); $note->show; ... # Update the notification later $note->body('Progress: 20%'); $note->show; ... # Take it off the screen $note->close; DESCRIPTION
Desktop notification objects are represented as objects of this class. They are created by a Desktop::Notify object. Displaying, closing, and modifying the notification is done by using methods in this class. METHODS
new $notify, %params This is called internally by Desktop::Notify to create a new notification object. show Display the notification on the screen. If this notification had previously been shown and not closed yet, it will replace the existing notification. Show can be called multiple times on the same notification, probably with attribute changes between calls, and later show calls will cause the server to seamlessly replace the existing notification. close Close the notification if it is already being displayed. ATTRIBUTES
The following parameters can be set when creating the object or later modified using accessors (descriptions are from the specification at <http://www.galago-project.org/specs/notification/0.9/x408.html>) summary The summary text briefly describing the notification. body The optional detailed body text. Can be empty. timeout The timeout time in milliseconds since the display of the notification at which the notification should automatically close. If -1, the notification's expiration time is dependent on the notification server's settings, and may vary for the type of notification. If 0, never expire. The following extra parameters are included in the specification but not supported by Desktop::Notify at this time app_icon The optional program icon of the calling application. actions Actions are sent over as a list of pairs. Each even element in the list (starting at index 0) represents the identifier for the action. Each odd element in the list is the localized string that will be displayed to the user. hints Optional hints that can be passed to the server from the client program. perl v5.10.1 2009-12-25 Desktop::Notify::Notification(3pm)

Check Out this Related Man Page

SIGEVENT(7)						     Linux Programmer's Manual						       SIGEVENT(7)

NAME
struct sigevent - structure for notification from asynchronous routines SYNOPSIS
union sigval { /* Data passed with notification */ int sival_int; /* Integer value */ void *sival_ptr; /* Pointer value */ }; struct sigevent { int sigev_notify; /* Notification method */ int sigev_signo; /* Notification signal */ union sigval sigev_value; /* Data passed with notification */ void (*sigev_notify_function) (union sigval); /* Function used for thread notification (SIGEV_THREAD) */ void *sigev_notify_attributes; /* Attributes for notification thread (SIGEV_THREAD) */ pid_t sigev_notify_thread_id; /* ID of thread to signal (SIGEV_THREAD_ID) */ }; DESCRIPTION
The sigevent structure is used by various APIs to describe the way a process is to be notified about an event (e.g., completion of an asyn- chronous request, expiration of a timer, or the arrival of a message). The definition shown in the SYNOPSIS is approximate: some of the fields in the sigevent structure may be defined as part of a union. Pro- grams should only employ those fields relevant to the value specified in sigev_notify. The sigev_notify field specifies how notification is to be performed. This field can have one of the following values: SIGEV_NONE A "null" notification: don't do anything when the event occurs. SIGEV_SIGNAL Notify the process by sending the signal specified in sigev_signo. If the signal is caught with a signal handler that was registered using the sigaction(2) SA_SIGINFO flag, then the following fields are set in the siginfo_t structure that is passed as the second argument of the handler: si_code This field is set to a value that depends on the API delivering the notification. si_signo This field is set to the signal number (i.e., the same value as in sigev_signo). si_value This field is set to the value specified in sigev_value. Depending on the API, other fields may also be set in the siginfo_t structure. The same information is also available if the signal is accepted using sigwaitinfo(2). SIGEV_THREAD Notify the process by invoking sigev_notify_function "as if" it were the start function of a new thread. (Among the implementation possibilities here are that each timer notification could result in the creation of a new thread, or that a single thread is cre- ated to receive all notifications.) The function is invoked with sigev_value as its sole argument. If sigev_notify_attributes is not NULL, it should point to a pthread_attr_t structure that defines attributes for the new thread (see pthread_attr_init(3)). SIGEV_THREAD_ID (Linux-specific) Currently used only by POSIX timers; see timer_create(2). CONFORMING TO
POSIX.1-2001. SEE ALSO
timer_create(2), aio_fsync(3), mq_notify(3), pthreads(7) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. GNU
2010-09-19 SIGEVENT(7)
Man Page