[wx-dev] RFC: wxNotificationMessage

[Vadim Zeitlin]

On Thu, 29 Nov 2007 17:28:03 +0100 Vaclav Slavik <vslavik at fastmail.fm> wrote:

VS> David Barnard wrote:
VS> > By contrast, some platforms only support clicking on the
VS> > notification itself. What happens in libnotify when you click on
VS> > the notification, not a button?
VS> 
VS> The notification is dismissed (at least in apps I tried). So we'd 
VS> probably want to only allow specifying one action on these platforms 
VS> and trigger it when notification is clicked -- and show (single) 
VS> button when using libnotify.

 I've implemented the Win32 version now (but not the libnotify one yet...
and I don't know when will I have time to do it to be honest) so I'd like
to decide how do we handle it now. Under Win32 there are no buttons and
clicking the notification does close it but it generates a different
message from the one used when the notification closes automatically on
timeout or because the user clicked on "x" button (although those two do
generate the same message, so we can't distinguish between them).

 So, indeed, we can generate some message when the user clicks on the
notification under Windows. However if the program is not interested in
them we probably don't want to add a button just to generate them under
Unix. Hence I propose to add "wxOK" as possible value to flags (see the
recently added wxNotificationMessage::SetFlags()) and only add the button
and generate the message if it's specified.

 What do you think?
VZ