Late in the development cycle of patch 10.1.7 many C_Ping functions were moved to a secure namespace. Among these are a handful of functions that don't perform any form of restricted interaction with the ping system, but instead either just query static data or access information like ping cooldowns.
Having these functions hidden away in the secure namespace makes it difficult for addons to provide any custom UIs that integrate with the system, such as custom ping wheels. It'd be helpful if the following functions could be moved back to the public C_Ping namespace and their restrictions removed.
C_PingSecure.GetPingCooldown - Unlocking this function would permit custom ping wheels showing a user feedback on whether or not they can send a ping.
C_PingSecure.GetDefaultPingOptions - Unlocking this function means a custom ping wheel doesn't need to hardcode all the available ping types.
Meorawr
commented
10 months ago
Late in the development cycle of patch 10.1.7 many C_Ping functions were moved to a secure namespace. Among these are a handful of functions that don't perform any form of restricted interaction with the ping system, but instead either just query static data or access information like ping cooldowns.
Having these functions hidden away in the secure namespace makes it difficult for addons to provide any custom UIs that integrate with the system, such as custom ping wheels. It'd be helpful if the following functions could be moved back to the public C_Ping namespace and their restrictions removed.