What's the process for deprecating / removing API. I've found at least
one example where this makes sense for Wayland:
/* @since 1.2 */
EAPI void-
ecore_wl_pointer_xy_get(int *x, int *y)
This function returns an x and y value saved into global variable in
the motion event handler - my guess was t
On Wed, 1 Aug 2012 18:40:24 +0100
"Bradford, Robert" wrote:
> What's the process for deprecating / removing API. I've found at least
> one example where this makes sense for Wayland:
>
> /* @since 1.2 */
> EAPI void-
> ecore_wl_pointer_xy_get(int *x, int *y)
>
> This function returns an x and y
On 01/08/12 18:40, Bradford, Robert wrote:
> What's the process for deprecating / removing API. I've found at least
> one example where this makes sense for Wayland:
>
> /* @since 1.2 */
> EAPI void-
> ecore_wl_pointer_xy_get(int *x, int *y)
>
> This function returns an x and y value saved into glo
>
> We can add eina_deprecated to it for now. Yes, it is a left-over from the
> global coordinates era ;) Although, please hold off on sending a patch for
> that because I need to verify (for other use cases which are in development)
> that this function is in fact safe to deprecate.
Sure - of cou
