Is it possible to resize dynamicly the window of the engine?
if not, it could be usefull to add a function for that...
dynamic resolution?
dynamic resolution?
-----------------------------
Sans danger, pas de gloire...
http;//bappy.free.fr
-----------------------------
Sans danger, pas de gloire...
http;//bappy.free.fr
-----------------------------
0. Sorry for a long post:)
1. In Windows OS it is possible a little bad horrible terrible HACK (here and almost always when you'd like to do something with Irrlicht window).
You can obtain window's HWND indirectly (e.g. by calling ::FindWindow function). And then you can send messages to this window. In this case you can send WM_SIZE message to it. But this is not enough in this case...
2. Anyway AKAIK, HWND property will never be public since it's os-dependent element and therefore cannot be a member of os-independent interface such as IrrlichDevice. So there are two ways - declare most of window functions in IrrlichtDevice and implement them in CIrrDeviceWin32 and CIrrDeviceLinux classes or just let people to make those little hacks The first way is much better for sure but much more time consuming as well...
3. BTW, Niko, would you like to implement a little bit different way of Engine Device creation: not to create your own window but attach to the already existed one passed as a pointer (void*) to IrrlichtDevice constructor, for example. It can be NULL for noobies or those who don't need it and then you will create your own window...
If you need to perform some actions in engine internally (such as in this case when you need to reset window size in CVideoNull object when window is resized) you can do all such stuff internally in your message handling function. This function can be called by user from his own message handling function. I mean this can be implemented as an option feature for "experienced users"
1. In Windows OS it is possible a little bad horrible terrible HACK (here and almost always when you'd like to do something with Irrlicht window).
You can obtain window's HWND indirectly (e.g. by calling ::FindWindow function). And then you can send messages to this window. In this case you can send WM_SIZE message to it. But this is not enough in this case...
2. Anyway AKAIK, HWND property will never be public since it's os-dependent element and therefore cannot be a member of os-independent interface such as IrrlichDevice. So there are two ways - declare most of window functions in IrrlichtDevice and implement them in CIrrDeviceWin32 and CIrrDeviceLinux classes or just let people to make those little hacks
The first way is much better for sure but much more time consuming as well...3. BTW, Niko, would you like to implement a little bit different way of Engine Device creation: not to create your own window but attach to the already existed one passed as a pointer (void*) to IrrlichtDevice constructor, for example. It can be NULL for noobies or those who don't need it and then you will create your own window...
If you need to perform some actions in engine internally (such as in this case when you need to reset window size in CVideoNull object when window is resized) you can do all such stuff internally in your message handling function. This function can be called by user from his own message handling function. I mean this can be implemented as an option feature for "experienced users"
there is another guest...