A little change in the engine would be great!

[Guest]

Hi. I've been researching to get an Irrlicht window in a GUI and it has been impossible to me. Maybe this is not impossible, but one thing is clear: it is quite difficult.
I'd like to make a suggestion.
If the createDevice function initialized the device and didn't open a window directly (this could be done in another function), it would be easier to map an irrlicht window wherever you want. That's all.
I know there's a gui for Irrlicht, but there are people who would like to use another GUIs and this makes it difficult I think.

[cartoonit]

createDevice(EDT_NULL);

I thought this doesn't create a window, does take the focus though, temporarily...

[niko]

If the createDevice function initialized the device and didn't open a window directly (this could be done in another function)

Or maybe a createDevice() function which would take a window handle as parameter?

[hybrid]

Hmm, is is enough to have a window handle? If I want to have an optimized PutImage function I still have to touch the code. Usually window and draw function are tightly related. Maybe another layer of abstraction is needed. When I started to add some more X11 extensions to the setup part I really got confused with the many different options I have to set or check in order to get the right function to be called. I also considered using SDL to draw the picture, but this is also almost impossible with the current device structure. Even worse, SDL is available for Linux and Windows - do I have to copy all code into both devices?
I did not check the IrrlichtNX structure yet, but they say that the device sturture has changed to make it easier to change such rendering issues!?

[Guest]

I don't think that optimizing the output to the new window is mandatory (of course, it would be useful) because most of the purposes of embedding an irrlicht window is making object editors and so on. Maybe this change would change many things.
Another thing I thought I could do is to simulate the embedding of the window and printing the window in an empty place of the wxFrame and substracting the window title if possible, and when I move the wxFrame, move the window the same amount of pixels. If this is not possible, I would like at least be able to put the irrlicht window always visible on the wxFrame, although I push the wxFrame. Any of these things are possible? Thanks a lot.

[he_man]

I know this is not related to a 3d engine, but look at this page. There are various functions that would be good to implement in Irrlicht, especially the ones that return the Xwindow id and the window handler.


http://www.fltk.org/doc-1.1/osissues.html

[hybrid]

Maybe XQueryTree could also help? If you start from the RootWindow you can search the tree until you find the Irrlicht window you'd like to get. Documentation is rather short, but google might help.

[Guest]

since this is not a trivial matter, I prefer doing first the frontend and events to the editor, and later I will do the irrlicht window stuff.