help me .who can also use code menu. plz terch me .
i need sample source code menu.
help me!! who has code menu. plzzzz
-
Baal Cadar
- Posts: 377
- Joined: Fri Oct 28, 2005 10:28 am
- Contact:
This is exactly the kind of posts, that have been discussed only recently: http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=11120
This post doesn't show the slightest bit of effort on your side to solve your problem. (whatever this is exactly, since your post completely fails to address it)
If you can't be bothered to even write in halfway acceptable english(even if you are not a native english speaker, I am sure you can do better than), I for sure can't be bothered to search my sources to find something that might be what you want.
So best try again. Write in proper language, describe what you want, describe what specific part of the work you had problems with.
This post doesn't show the slightest bit of effort on your side to solve your problem. (whatever this is exactly, since your post completely fails to address it)
If you can't be bothered to even write in halfway acceptable english(even if you are not a native english speaker, I am sure you can do better than), I for sure can't be bothered to search my sources to find something that might be what you want.
So best try again. Write in proper language, describe what you want, describe what specific part of the work you had problems with.
-
Baal Cadar
- Posts: 377
- Joined: Fri Oct 28, 2005 10:28 am
- Contact:
This is not a question of being a newbie or not. This is a question of how to present your problem to the people you want help from.
You basically want a favor. That's ok. Enough people around willing to grant one. But it is important to do it right, else you get answers like mine from above.
Here are a few pointers (stolen from the Ogre forum rules, only a selection I found most important)
Always search the forum and the Wiki before posting. You should also familiarise yourself with the API and Manual.
Summarise the topic accurately in the headline. For example "HELP!!" is not a valid headline, nor is "What is going on?". A good headline might read "alpha_reject behaving differently on GL rendersystem".
Do your homework first. Investigate your problem by experimenting with variations, looking at logs, and using your debugger. Problem solving is a learned skill, you have to DO it to become self sufficient. We're happy to help but expect some effort from you too.
Post just the pertinent details and explain what you've tried and what you've looked at already. Don't just post your entire codebase, say "it doesn't work!" and expect people to sort it out for you.
Be succinct. State the problem, the symptoms, the investigation in a structured and easy to read form. Blocks of rambling text will just get you ignored.
Post in proper English. If English isn't your first language, we'll cut you some slack, but there is no excuse for native English speakers to post contraction-filled, badly punctuated, grammatically random posts. This isn't a text message, people, and continually using contractions like 'U' and 'ur', and interspersing every second sentence with 'lol' will lead me to stop caring what you have to say in short order.
Don't 'bump' threads unless you have something more to add. If you didn't get a response the first time, it's likely that you didn't provide enough information, or people thought you hadn't done enough work of your own to justify a response. Or, they just might not have known the answer.
You basically want a favor. That's ok. Enough people around willing to grant one. But it is important to do it right, else you get answers like mine from above.
Here are a few pointers (stolen from the Ogre forum rules, only a selection I found most important)
Always search the forum and the Wiki before posting. You should also familiarise yourself with the API and Manual. Summarise the topic accurately in the headline. For example "HELP!!" is not a valid headline, nor is "What is going on?". A good headline might read "alpha_reject behaving differently on GL rendersystem". Do your homework first. Investigate your problem by experimenting with variations, looking at logs, and using your debugger. Problem solving is a learned skill, you have to DO it to become self sufficient. We're happy to help but expect some effort from you too. Post just the pertinent details and explain what you've tried and what you've looked at already. Don't just post your entire codebase, say "it doesn't work!" and expect people to sort it out for you. Be succinct. State the problem, the symptoms, the investigation in a structured and easy to read form. Blocks of rambling text will just get you ignored. Post in proper English. If English isn't your first language, we'll cut you some slack, but there is no excuse for native English speakers to post contraction-filled, badly punctuated, grammatically random posts. This isn't a text message, people, and continually using contractions like 'U' and 'ur', and interspersing every second sentence with 'lol' will lead me to stop caring what you have to say in short order. Don't 'bump' threads unless you have something more to add. If you didn't get a response the first time, it's likely that you didn't provide enough information, or people thought you hadn't done enough work of your own to justify a response. Or, they just might not have known the answer.-
Baal Cadar
- Posts: 377
- Joined: Fri Oct 28, 2005 10:28 am
- Contact:
No bad day. Actually I am helping this guy/gal by providing informations that help on information retrieval and in getting answers he/she really wants. Don't feel, that I am doing something wrong or be disrespectful at all.
dhenton9000, feel free to correct me in what I wrote, when I got something wrong.
dhenton9000, feel free to correct me in what I wrote, when I got something wrong.
-
Eternl Knight
- Posts: 313
- Joined: Tue Nov 01, 2005 5:01 am
)-
Guest
-
Eternl Knight
- Posts: 313
- Joined: Tue Nov 01, 2005 5:01 am
-
Guest