You're right.
Also it should be "fVw / fVh" because is width and height to calculate the OpenGL viewport relation.
Anyway the result was that graphics were a a bit deformed.
You're right.
Also it should be "fVw / fVh" because is width and height to calculate the OpenGL viewport relation.
Anyway the result was that graphics were a a bit deformed.
No signature provided yet.
The worst thing I did, was try to convert a visual basic app to delphi. It was a totaly mess and a big waste of time. What I learn? never again convert someone else code, specially if it comes from visual basic. It's better to build new things with new approaches. No matter how well writen the original code is, in the end it's always a different way to see and do things, and an incompatible programming philosophy, it's bad if you have only code and zero documentation. I had to refuse the job, but instead I accepted it.
I would take that challenge But surely there are may coding differences between Pascal and Basic language, that force you to plan some things differently.
http://govnokod.ru/pascal
Prepare your facepalm cannon.
Actually I like doing that!!! I think it is more readable than:Code:FVar : Booelan; if FVar = True then begin ... end;
Code:if FVar then begin ... end;
Not that i have ever done this, but i can imagine the above code would be about same as this
Let's hope the compilers know how to optimize the extra comparison out of executable.Code:if (a = b) = True then begin ... end;
I can't see why a compiler should have a hard time optimizing the code. It seems to me, it would be simple to add a rule saying something like:
This should be quite easy when you've made a syntax tree.Code:if our code says boolean = True then replace the code with boolean
Imagine I've written something clever here inspiring you to make something awesome. If that happens give me credits
Ah ok, then I misunderstood you
Imagine I've written something clever here inspiring you to make something awesome. If that happens give me credits
Bookmarks