fix(linux): cast notification callback with NOTIFY_ACTION_CALLBACK

[chewi]

Description

This fixes an incompatible pointer type error with GCC 15.

third-party/tray/src/tray_linux.c: In function ‘tray_update_internal’:
third-party/tray/src/tray_linux.c:103:87: error: passing argument 4 of ‘notify_notification_add_action’ from incompatible pointer type [-Wincompatible-pointer-types]
  103 |         notify_notification_add_action(currentNotification, "default", "Default", tray->notification_cb, NULL, NULL);
      |                                                                                   ~~~~^~~~~~~~~~~~~~~~~
      |                                                                                       |
      |                                                                                       void (*)(void)
In file included from /usr/include/libnotify/notify.h:27,
                 from third-party/tray/src/tray_linux.c:19:
/usr/include/libnotify/notification.h:202:85: note: expected ‘NotifyActionCallback’ {aka ‘void (*)(NotifyNotification *, char *, void *)’} but argument is of type ‘void (*)(void)’
  202 |                                                                NotifyActionCallback callback,
      |                                                                ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
/usr/include/libnotify/notification.h:120:19: note: ‘NotifyActionCallback’ declared here
  120 | typedef void    (*NotifyActionCallback) (NotifyNotification *notification,
      |                   ^~~~~~~~~~~~~~~~~~~~

/**
 * NOTIFY_ACTION_CALLBACK:
 * @func: The function to cast.
 *
 * A convenience macro for casting a function to a [callback@ActionCallback].
 *
 * This is much like [func@GObject.CALLBACK].
 */
#define NOTIFY_ACTION_CALLBACK(func) ((NotifyActionCallback)(func))

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud