[NEW VERSION] - 28 Oct 21 Changed: Retracting multiple notifications in close succession could lead to a fatal "array subscript out of bounds" error - added a check to prevent this. ================================== [NEW VERSION] - 26 Apr 19 Added: _Notify_RetractCheck allows the user to determine the retraction method (title clicked/message clicked/timeout) and content (title/message) of the last retracted notification. ================================== [NEW VERSION] - 2 Aug 18 Added: When specifying the icon to use, if the $vIcon parameter is set to the name of an ico or exe file, the main icon within will be displayed, but if a trailing "|" followed by the icon index is added to the name, that icon from within the file is used. ================================== [NEW VERSION] - 4 Jun 17 Added: _Notify_Locate now takes an optional second parameter which, when used in a multiple monitor setup, will force the notifications to appear on a specified monitor rather than the left and right side of the entire display area. ================================== [NEW VERSION] - 15 Aug 15 Changed: If the display is full of existing Notifications, any new ones are kept hidden until space becomes available - in the past these were not created and an error returned. Note that any timeout applied to these initially hidden Notifications only commences once they become visible - otherwise they risked never being seen at all. ================================== [NEW VERSION] - 13 Jul 15 Added: •A new function _Notify_Modify which allows you to change the colour, text and/or click setting of an existing notification. •A new $sGUID parameter for _Notify_Set to set the "title" of the notification GUI - this allows WinList to list all current notifications New Example 2 shows these 2 additions working ================================== [NEW VERSION] - 11 May 15 Changed: New code to cater for multiple monitors. ================================== [NEW VERSION] - 7 May 15 Changed: New code to prevent multiple clicks overwhelming the UDF - further clicks now ignored if a notification is extending/retracting. ================================== [BUGFIX VERSION] - 16 Jul 14 Fixed: Bug when adding a PNG in x64. ================================== [New Version] - 2 Jun 14 Some Global variables were renamed in AutoIt v3.3.12.0 - code updated to match. ================================== [New Version] - 30 Jan 13 New: Notifications can now: - Stay almost hidden in the border until you click them on them to display. - Fade in/out as well as slide - either mode can be set as default or on an individual basis. - Appear/disappear at user-defined speeds - again these can can be set as default or on an individual basis. Thanks to z0iid for the suggestions. Fixed: A couple of bugs - thanks BrewManNH. =================================== [New Version] - 23 Feb 12 New: - _Notify_Hide function allows user to programatically retract notifications. _Notify_Show now returns handle of the notification - passing this handle to _Notify_Hide retracts it. See example for more detail. Thanks to z0iid who asked for the feature. =================================== [New Version] - 7 Jan 12 New: - _Notify_Locate function allows user to select location and direction of notifications: ; Syntax ........: _Notify_Locate($iLocation) ; Parameters ....: $iLocation - Start point and direction for Notifications ; 0 = Bottom right upwards (default) ; 1 = Top right downwards ; 2 = Top left downwards ; 3 = Bottom left upwards[/code] Changed: - Notifications can show images (32x32 only - just use the full path as the parameter). Thanks to UEZ and Yashied for the code to enable PNG images to be used. - [i]_Notify_Set[/i] has a further parameter to get the notifications to slide into place rather that moving instantly. They still move pretty quickly as they are actioned inside a message handler and I do not want to hold up the queue for longer than absolutely necessary. The more notifications there are to move the quicker they slide - on my machine it takes about 250ms to move 17 of them which seems not to cause any problems. CYA: This a "user beware" option. Thanks to czardas for the feature request.