I hope now its clear that how I am creating OpenGL display inside the
Fl_Double_Window. The code is...
MainWindow = new Fl_Double_Window(WINDOW_SIZE_W, WINDOW_SIZE_H, "3DRACS
(v1.1.0)");
.
.
MainMenuBar = new Fl_Menu_Bar(0, 0, WINDOW_SIZE_W, 25);
.
.
MainWindow->show(argc, argv);
MainWindow->begin();
glutInitWindowSize (WINDOW_SIZE_W, WINDOW_SIZE_H-45);
glutInitWindowPosition (0, 25);
glutInitDisplayMode (GLUT_DOUBLE | GLUT_RGBA | GLUT_DEPTH | GLUT_MULTISAMPLE);
GLUT_MAIN_WINDOW = glutCreateWindow("3DRACS (v1.1.0)");
MainWindow->end();
.
.
Fl::run();
now could you tell me, why shortcut keys only work when I open that specific
menu.
Thanks.
> On 31.08.2012, at 17:04, Furqan <furqan...@hotmail.com> wrote:
>
> > No I am not using any kind of GlWidget of fltk for OpenGL display. I =
> am using the traditional OpenGL subroutines and added into =
> Fl_Double_Window. In this way, I created a menu bar in Fl_Double_Window.
>
> So you create an OpenGL window using functions from the operating =
> system, and you use FLTK to stitch another window into or next to the =
> OpenGL window? I am not clear how you get both to work together, in =
> particular event delivery is a problem, just like you encounter.=20
>
> Do you have two event loops? The OpenGL one and the FLTK one? How did =
> you create the OpenGL window exactly and when in the process?
>
> FLTK expects to receive ALL events from the operating system and then =
> distributes those to the correct windows and widgets. Having a second =
> even delivery systems makes it hard or impossible to know what event is =
> delivered where.
>
> Have you considered using Fl_GL_Window in your application? This would =
> make all the window layering and event delivery work correctly.
>
> A working and copilable source code file that exhibits the bug would be =
> extremely helpful.
>
> - Matthias=
>
_______________________________________________
fltk mailing list
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk
