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 global variable in > the motion event handler - my guess was that this was leftover from > when there were global co-ordinates available in the motion event > handler. > > Now since there are only surface relative positions - these values are > not particularly helpful and probably downright confusing since they > will change depending on what surface has focus. > > How can we mark this as deprecated and ultimately remove it? > > Cheers, > > Rob >
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. Cheers, dh ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
