[Octave-bug-tracker] [bug #44426] ginput with Qt doesn't return values for clicks outside axes

[Mike Miller]

Follow-up Comment #2, bug #44426 (project octave):

This is due to differences in how the buttondownfcn callback works between Qt
and FLTK. The ginput function is using buttondownfcn, but maybe it should be
using windowbuttondownfcn instead to ensure that clicks anywhere in the figure
are caught.

However, in FLTK when the windowbuttondownfcn callback is used, the mouse
coordinates from the "currentpoint" property of the axes lag one click behind.
But with the Qt toolkit the "currentpoint" property is correct when the
windowbuttondownfcn callback is called.

Seems to me like the Qt behavior is better, but fixing this for Qt using
windowbuttondownfcn would break ginput for FLTK.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44426>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/