Irrlicht Engine

Acki wrote: I realy don't see what's wrong with this code... :shock:
When I had the problem it was not obvious where the error is located, because it also could be that there are some bugs with some other GUI elements (like the focus bug) that could caused this, so it's always a good idea to post the whole creation of all gui elements in such a case... ;)
and there is realy not much more than that in this code...

Well, that's one reason why you should reduce it. If you had removed it before posting, then you would already have known that the other elements did not cause the bug as the bug would still have shown. If the bug would have been removed you would also already been able do give additional information. It's simply easier the less lines you post, really - that's all :-)

Acki wrote: there are many other posts that shows complete programs that's realy not neccesary and many codes are bad or even not formatted and commented and some are even not inside the code tags...

Yeah, but you're an experienced coder so your requirements are higher ;-) Hey, it wasn't that bad - just could have been even better.

Gee, that was a joke because of your strange comment "this won't work for you, because it uses new IrrExtensions" - you could still show it...
Moreover, it's pretty funny that you (the one who always tells the people how to proceed with return values in OnEvent) made such code But you really shouldn't take it this hard, it simply can happen to everyone. And all of us just wanted to help you (in a definitely friendly way)

I don't take this hard, and I don't want to fight someone, I just want to know what's so bad about the code I posted...

Of course I could show the IrrExtensions code too, there's nothing secret about it, I simply removed it because the error wasn't there definatly and you couldn't get the code to compile if the code was there, maybe I should just commented them out (but then the code would be about double as long)...
But you will see this code soon, because it's an example for a new extension...

About the return thing, you're right, and this example shows that I'm right with this, but if you look I added all returns like I always told, I simply didn't recognised that the default block always returns true...

hybrid wrote:And all of us just wanted to help you (in a definitely friendly way)

never thought something else, again: I just want to know why the code is bad for posting here, like CuteAlien said...

CuteAlien wrote:Yeah, but you're an experienced coder so your requirements are higher Hey, it wasn't that bad - just could have been even better.

yeah, if I knew where the error was I just posted this line, or wait, no I didn't post this, because I then knew what the error was...

Acki wrote: yeah, if I knew where the error was I just posted this line, or wait, no I didn't post this, because I then knew what the error was...

You still could have reduced it further without our help. That was and is the point I was trying to make too hard. Well, one of 'em. The other was that your indention is confusing me ... when you have two closing brackets, like } } then the second should never be more to the right then the first one imho.

I don't know how to say in english, so a last german one, for this thread:
Man kann einer Laus auch in den Arsch schauen !!!:lol:

and I try to translate: you also can look a lice into his a**hole !!!

well, I'm getting bored about this, you can't tell me a good reason why the code is bad to post, so I'm sure you just want to tell me I did something wrong, just to tell me that I did something wrong...

Acki wrote:<snip> you can't tell me a good reason why the code is bad to post <snip>

On last count I told you by now 5 times explicitly and implicitly that the thing that was bothering me was that you could have tried to reduce the code more. But I suppose I just spend the rest of the evening typing this some more times, cause why stop when you're having so much fun...

Or do do you miss to see the advantage of having to read shorter code when searching for bugs? I'm getting too confused figuring out what it is I am missing to write here, so I guess I simply give up now.

you told me 5 times the same and I answered 5 times the same: what's so bad about this ???
This is not a good reason why the code is bad to post here...
I also told you if you don't want to read more than 5 lines of code, then simply don't do it (I did it many times when the code was realy bad)...

You're just trying to find even the smallest mistake I made, just to have a reason to correct me...
That's something I never did and will never do, when I correct someone than it has hand and foot (also don't know how to say in english, but you'll understand what I mean)...
O.K, sometimes I be a little bit sarcasmic, but than you'll see that it's sarcasm...

btw, it would have taken you lesser time to read the code than doing this converation...

If you re-read my post you will notice that I actually never said anywhere that your code is bad. Critic isn't meant to put you down. And you can be sure I wouldn't have posted if I had imagined this thread in ahead.

Acki, the thing is that you annoyed us with boring list box entries. There's no reason to leave that code in. You simply gave the impression that only your holy grail's irrExtensions code is worth removing, while you don't need to put any effort in the rest of the code. It's a bad attitude to deliver code for external debugging without showing your own efforts.
Being granted that you can still do so, it's also allowed to mention it (and also to keep doing so every time you freak out about it).
So yes, you could have put more work into your code snippet before asking here. At least to give a good example for all the noobs that do it just like you did this time.

I still don't get what's wrong with it...
I wish most of the noobs would post their code like I did...
Maybe it looks like I'm hiding the IrrExtensions code, but I told you also that I just removed it because you won't be able to compile it...
This extension is that unsecret that I even will post the code into the code snippet forum !!!
Also non of my extensions are secret, you just need to know how to read a XML file...

I appreciate all your help, but this converation went prety pointless...

Now I won't look at this thread again, so if someone posts an answer/comment I will not see it and therefore not reply to it...

Acki wrote: Now I won't look at this thread again, so if someone posts an answer/comment I will not see it and therefore not reply to it... ;)

But then again you're to curious to resist... ;-)

may I suggest large quantities of beer and some InstaGib UT (Facing Worlds)
always does the trick for me