[Octave-bug-tracker] [bug #32178] fltk backend: ginput arguments

[Jan Hieronymus]

Follow-up Comment #7, bug #32178 (project octave):

I'm not an fltk expert, but at least I could figure out a quite simple patch
in order to get the correct button (1,2,3). This patch was applied to octave
3.6.2.

As I'm not yet familiar with diff/changesets etc. I'll propose the patch in
here. Two files need to be changed:


__init_fltk__.cc in line 1272 (case FL_PUSH:)
call
fp.execute_windowbuttondownfcn ();
with argument
Fl::event_button()

fp.execute_windowbuttondownfcn (Fl::event_button());


__fltk_ginput__.m in function ginput_windowbuttondownfcn
The second argument (data) will be set to 1,2,3 (left, middle, right) mouse
button.
Then just use 
button = data;
instead of
button = 1;


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/