On Thu, Jun 9, 2011 at 5:06 AM, MacArthur, Ian (SELEX GALILEO, UK)
<ian.macarthur-U45sO15dH+4/9X/9vyvaIQ@public.gmane.org> wrote:
>
> At some point, fltk-3 will offer a choice...
>

Seeing as the primary reason for this behavior in FLTK1 was for
backwards compatibility with Forms and the far more common behavior is
parent-relative coordinates (plus when would you *not* be referencing
x() and y()?), I would expect FLTK3 to use parent-relative coordinates
and only provide the old system in the FLTK1 compatibility layer.