t; > On 30/11/11 08:20, Terry Welsh wrote:
> > > Hi,
> > > I'm using FLTK 2, and I have a class derived from GlWindow. My handle()
> > > function gets called for almost every key on the keyboard, but not when I
> > > press backspace or delete. Is this
> On 30/11/11 08:20, Terry Welsh wrote:
> > Hi,
> > I'm using FLTK 2, and I have a class derived from GlWindow. My handle()
> > function gets called for almost every key on the keyboard, but not when I
> > press backspace or delete. Is this expected behavior? I
Hi,
I'm using FLTK 2, and I have a class derived from GlWindow. My handle()
function gets called for almost every key on the keyboard, but not when I press
backspace or delete. Is this expected behavior? Is there a way to get events
for these keys?
x, but it
hasn't helped me so far. I'll be studying it some more unless anyone has a
better idea...
> Am 02.12.2009 01:06, schrieb Terry Welsh:
> > I'm using fltk2 on Linux and trying to open 3 GlWindows on 3 separate
> > displays. My best guess at how to do this
I'm using fltk2 on Linux and trying to open 3 GlWindows on 3 separate displays.
My best guess at how to do this is to follow the instructions in x11/run.cxx
and change the value of fltk::xscreen immediately after calling open_display().
I tried to do this by overriding Window::show(), but ther
Well, I'm still not sure what to do to fix the logic here. When a button is
pushed, the PUSHED flag is set but the STATE flag is not. Seems to me they
mean the same thing, so I don't know why they're being handled differently. In
any case, for anyone else with this problem, you can just use B
Button::value() is always returning false. It appears this was caused by a
change to the the handle function's DRAG logic in Button.cxx (lines 91-108)
that happened from version 2.0.x-r5734 to 2.0.x-r5940. So far I haven't been
able to narrow it down any better than that. Does anyone know of
Never mind. This behavior and the workaround I needed are already documented
in Input.cxx. Just took me a while to find it
> Hi. I have a WordwrapInput window set up to call a callback on
> WHEN_ENTER_KEY. This part works. Unfortunately, the callback also gets
> called if there is any
Hi. I have a WordwrapInput window set up to call a callback on WHEN_ENTER_KEY.
This part works. Unfortunately, the callback also gets called if there is any
new text in the WordwrapInput and I go and click on another widget. Has anyone
else had this problem? Is there a workaround for it?
__
9 matches
Mail list logo
