Hi,
Can I use FLTK to develop a GUI with panels where I can, for example, drag
& drop different tabs from different dialogs/panels to other dialogs/panels
- in short, move action items to menus, toolbars, panels, create new
panels, etc. That is, can I use FLTK to create a dynamic GUI like that of
On 11 Apr 2013, at 18:34, Greg Ercolano wrote:
> I guess we should see how Win32 and OSX behave, and if they're
> "reliable"
> as well, we should either:
>
> 1) Document the OS specific behavior, whether different or same,
> and leave the code alone
> 2) Pick one
> > //hH
> > int Sbut::handle ( int event )
> > {
> > if ( event == FL_PUSH )
> > {
> > cout << "Sbut handle 1: PUSH " << endl;
> > do_callback();
> > return 1;
> > }
> > return 0;
> > }
>
> Also, unrelated, the above bit of code should be r
On 04/11/13 02:18, MacArthur, Ian (Selex ES, UK) wrote:
>> If I understand correctly, the capslock state info is correct during
>> regular keypresses, just not when the capslock key is hit.
>
> Yes - in all the tests I tried, the Caps Lock state was always "correct"
> during (and after)
Thanks,
I have implemented functions to control the menu behaviour, patch submitted as
feature-request STR #2950.
The implementation is very conservative (does not change current behaviour) not
to break current applications but adds the programmer various possibilities how
to control when the i
> I have found some problems with the file chooser on AIX and NetBSD
> operating systems and opened STR #2935 with a patch to fix them:
> Selecting "File systems" from the menu shows either nothing (not even
> the root filesystem on AIX) or many entries that make no sense or are
> not available (li
Hi,
I have found some problems with the file chooser on AIX and NetBSD
operating systems and opened STR #2935 with a patch to fix them:
Selecting "File systems" from the menu shows either nothing (not even
the root filesystem on AIX) or many entries that make no sense or are
not available (like sw
> If I understand correctly, the capslock state info is correct
> during
> regular keypresses, just not when the capslock key is hit.
Yes - in all the tests I tried, the Caps Lock state was always "correct" during
(and after) regular key presses.
However, any attempt to discern the C
8 matches
Mail list logo
