On 03/25/13 07:53, testalucida wrote:
> I just overlooked the which( x, y ) method which exactly fits my needs.
Great -- yes, it's easy to miss, because it wasn't documented! ;)
Fixed in r9849:
-
Fl_Widget * F
On Mon, 25 Mar 2013 08:52:22 -0700, humpty wrote:
>I have a window with full of widgets made with fluid. Some of them
>are text fields to be user filled in order.
>
>When I hit the tab key to change widget focus, the ordering is haphazard.
>
>Do widgets in groups have a tab-key ordering ? How do
thank you guys for caring about my problem
have a nice day
testalucida
> > On 03/25/13 05:16, testalucida wrote:
> > > _
> > > /x\ o
> > >
> > > I'm interested in click "x" but not in click "o".
> > =
>
> > What Ian said, and I'd offer that setting when(FL_WHEN_NOT_CHANGED)
> >
The Tab navigation is in the order on which the widgets were created. The arrow
navigation takes their position and size into account.
"MacArthur, Ian (Selex ES, UK)" schrieb:
>
>> I have a window with full of widgets made with fluid. Some of them
>> are text fields to be user filled in order
> I have a window with full of widgets made with fluid. Some of them
> are text fields to be user filled in order.
>
> When I hit the tab key to change widget focus, the ordering is
> haphazard.
>
> Do widgets in groups have a tab-key ordering ? How do you change the
> order? Can you change the
I have a window with full of widgets made with fluid. Some of them
are text fields to be user filled in order.
When I hit the tab key to change widget focus, the ordering is haphazard.
Do widgets in groups have a tab-key ordering ? How do you change the order? Can
you change the ordering between
> On 03/25/13 05:16, testalucida wrote:
> > _
> > /x\ o
> >
> > I'm interested in click "x" but not in click "o".
>
> What Ian said, and I'd offer that setting when(FL_WHEN_NOT_CHANGED)
> /should/ work for your case, but does not.
Yes; I tried that too, to no avail...
However,
Hi Ian,
excuse me bothering you... it's much easier than I thougt: I just overlooked
the which( x, y ) method which exactly fits my needs.
Thanks for answering.
> > imagine a Fl_Tabs instance with only one "card".
> > Clicking on its tab will not result in a callback action.
> > Catching the F
You could perhaps use the method:
Fl_Widget * Fl_Tabs::which (int event_x, int event_y)
in your derived handle().
e.g.
int handle( int e)
{
if (e==FL_PUSH)
{
if ( which(Fl::event_x(), Fl::event_y() )
{
// pushed into the 'x'-region
}
else
{
On 03/25/13 05:16, testalucida wrote:
> _
> /x\ o
>
> I'm interested in click "x" but not in click "o".
What Ian said, and I'd offer that setting when(FL_WHEN_NOT_CHANGED)
/should/ work for your case, but does not.
This is probably a bug in Fl_Tabs; I opened STR#2939
> imagine a Fl_Tabs instance with only one "card".
> Clicking on its tab will not result in a callback action.
> Catching the FL_PUSH event provides the position of the mouse-click but
> I don't know the click occuring within the tab or somewhere right of
> it.
> Is there a way how to get the tab g
Hi,
imagine a Fl_Tabs instance with only one "card".
Clicking on its tab will not result in a callback action.
Catching the FL_PUSH event provides the position of the mouse-click but I don't
know the click occuring within the tab or somewhere right of it.
Is there a way how to get the tab giving t
> The 2.0.x branch is missing from the download area and the trunk does
> not compile out of the box.
Note that these two observations may not be un-related...
fltk-2 is, as you know, deprecated, and no one is available to maintain nor fix
it, so we can't really go on distributing it, until it
13 matches
Mail list logo