Irrlicht Engine

deps wrote:

2. One guru-programmer said that if you write your best code then you, by definition, has not enough skill to debug it. (it means also "to assess" it )

iirc, it was Linus Torvalds who said it.

It doesn't make this false

))

DevCPP ONLY uses int main()

Now I'm a believer Yeah, DevCpp is rulez!

Ok :)

2Liquidream :
Couple advices to a great supplier :) (really, no offence)
What I would do in such situation
1. I'm pretty sure that your program's entry point is not WinMain function, but you can debug it (set breakpoint in the very beginning of your WinMain function and check if program ...

If you're a little newbie with C++ and have access to MSVC then use it. And don't be so rude to call it M$ cause anyway atleast it's the best Development Environment for C++ today.

BTW, you don't give any chance o DevC++ by using it instead of MSVC cause they are not even competitiors and never ...

Robomaniac: it's a kind of storming - I know this.
A little advice: think a lot before write a single line of code. No offence it really helps. I mean, firtst try to determine how your project will look like:
1. Technical tasks.
2. GUI (according to 1)
3. Development stuff...

Development stuff ...

I think that the way of rt is better mainly because of one simple reason:

Saigumi has to change his wrapper every time new function appears in the ISceneManager intereface, but rt doesn't ;)

P.S.: just a mall not for Saigumi: I hope you posted here not your code but just an example from your mind ...

there was already a post somewhere on how to find collision point. The answer was to create your OWN collision response animator (you can inherit it from the existing one). So I think you have the same question.

Search forum before posting...

2keless: I have MSDN - thank you. But if you have ever tested your code for meeteing any code style then you should know that almost all of them give exactly this situation as an example how you don't have to write your code ;)

2Guest: almost the same ;) it's always better to set brackets than do ...

one more thing...

Niko, it's not a big problem to set up compiler and linker options in main.cpp file in examples/tutorials. So this way you can avoid all those questions about "I have a lot of errors during my compilation in VC60", etc... I mean if you link your library with #pragma comment(lib ...

yes, I agree, VA is good.

But don't tell that VS is MUCH worse - you just have to know how to set it up with your own color scheme and so on.
As about defines then VA shows them in tooltip and if they are long enough (which is very common case) it's not very useful... BTW, in VS you just need to ...

no. it useless cause 'break' breaks switch :)

1. I would recommend you ALWAYS use brackets when you are not sure about operators precedence. I have 7 years experience in C/C++ but I'm not sure which one is the first - 'comparison' or 'logical and'. Of course, you can use help but this makes your ...

BTW, there is one more obvious... with CGUIFileOpenDialog, actually with its ScrollBar...
It doesn't calculate the size of the scroll thumb correctly until you don't move it. Initially it's always very thin. Try Userinterface demo.

And one more: it's not a bug but a useful feature. It would be very ...

strange...
look carefully in techdemo. look on the sky...
there are tree small rays in the "corner" going from the same point. I can see it . In another corner I can see just one ray.
Actually, rays are segments.

I can send you screen shots via email...

If someone uses something like Ctrl+Space or Ctrl+Shift+Space then they should know this

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 ...