I am using fltk 2 for sure because I am big c++ guy. I've seen no mention of the functionality I need being deprecated or altered anywhere...though this could be due to the maturity of fltk 2.0.
I could let fltk create all the things mentioned and pass them on I suppose but then I am left with what fltk will give me. Nothing more nothing less. I can give up on programmtically setting FSAA for instance but I would really not want to do that. This is just an example. I will of course understand if what I am attempting to do just isn't possible. I and others will be very disappointed but that wouldn't mean we wouldn't consider the fltk API to be great. To be clear giving up on this is an option. I just don't want to quit fighting yet :) I will do as you suggest if no better options emerge for me though. > =20 > > > I need a handle on the display, visual, etc that fltk uses so=20 > > that I can load other libraries that I am using. > >=20 > > I am developing and interactive 3D application. For example,=20 > > another library I am using the Object Oriented Input System=20 > > library so that I can query multiple instances of keyboards,=20 > > mice, or joysticks. I must initialize the OIS by supplying a=20 > > Diplay*, XVisualInfo* etc. > > Yup, OK. You can just create all that stuff in fltk in the "normal" way, > then recover the display etc that fltk has created and pass that on. > > > You must have seen my previous post about Gl contexts as I=20 > > didn't mention it here. However, if I do get the native=20 > > handles to work then my problems there would be solved there=20 > > as well most specifically I would be able enable=20 > > multisampling anti-aliasing for all the platforms I support. > > Yes - I have been reading your posts. I just haven't understood where > you were going, and didn't feel I had anything useful to say. I suspect > others are in the same boat and that's why you got no responses. Ask me > simple questions, I'm much better with them. > > > What I want to achieve is this: > > Initialize the the X display, visual, screen and colormap. > > Set these as the globals fltk will use before any windows are shown. > > Use these to initialise other libraries: opengl, ois, etc. > > Have fltk process gui events. > > Have OIS process HID input events. > > Have Opengl draw scenes. > > etc. > > What I do is let fltk create all the Xwindows and GL contexts itself, > rather than trying to pass it one I made elsewhere. > > Then I get things that fltk has made and pass them to other things as > need 'em. > > Can that not work for you? > > I don't know enough fltk-2 to say how it would do this, but in fltk-1.x, > well, see (what used to be) Appendix F of the manual and see if that > helps: > > http://www.fltk.org/doc-1.1/osissues.html#osissues > > http://www.fltk.org/doc-1.3/osissues.html=20 > > I don't know where the equivalent stuff is documented for fltk-2, if at > all. > > But anyway, you can probably create your window, then make it current > with=20 > mywindow->make_current(...) or whatever fltk-2 does, then you can read > the values set for=20 > > extern Display *fl_display; > extern Window fl_window; > extern GC fl_gc; > extern int fl_screen; > extern XVisualInfo *fl_visual; > extern Colormap fl_colormap; > > And that takes you some way to where you want to go, I think? > > > > > > > > > SELEX Sensors and Airborne Systems Limited > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS= > 14 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
