Beginning in Qt with OpenGL
-
I have re-installed the SDK... Now the errors are gone ,.. and application is running successfully.. except I'm not getting the exact output....
@Chuck.Gao : what was the output you got with the project?
The Project type is Qt Mobile Application , doesn't it support OpenGL and should I go for OpenGL ES...
-
[quote author="Chuck.Gao" date="1306134308"]no, it's OK for me. Maybe there have some problem with your environment or SDK, i'm not sure. You can paste the log on this thread, i think someone can resolve your problem[/quote]
You said that you got my app running on your sdk... right?
did you get any output in that?I have drawn a triangle in that app...
how to use OpenGL ES with QT
-
[quote author="Chuck.Gao" date="1306221357"]I can build it on both Desktop(also simulator) and Symbian device, but it’ll crash some where.
[/quote]You mean the application that I sent you will crash somewhere,...
[quote author="Chuck.Gao" date="1306221357"]Qt will use OpenGL ES automatically if you build Symbian based application.
[/quote]Then why is it not working.... I got the simulator window opened but the triangle is not drawn on the screen...
-
When I started debugging...
A Warning is shown..
It says..bq. The preferred debugger engine for debugging binaries of type 'x86-windows-msvc2008-pe-32bit' is not available.
The debugger engine 'Gdb engine' will be used as a fallback.
Details:There is no CDB binary available for binaries in format 'x86-windows-msvc2008-pe-32bit'What does that mean?
-
[quote author="ZapB" date="1306222858"]Which build are you trying to debug? Desktop/simulator/symbian? I would try getting it working on the desktop first.[/quote]
That was Qt Simulator -> N900 simulator
I tried that with desktop simulator,... It says Debugging starts..
It does nothing...No window appears... no output...
This is a Qt Mobile application...
-
That was the desktop target...
This is the report when I interrupt debugging...
bq. Debugging starts
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4 in read in psymtab, but not in symtab.)if you don't mind of testing my app yourself, I can mail you the project.... do you?
-
Guys I got it .....
I didn't use show function... now only i did...
Thanks for all your help..... :D
-
I have one more problem...
In this project , I'm drawing a triangle in center of the screen...
The project clears the screen with the color I specified , but it doesn't draw the triangle...
Here is the code...
@GamePlay::GamePlay(QWidget *parent) :
QGLWidget(parent)
{
setFormat(QGLFormat(QGL::DoubleBuffer | QGL::DepthBuffer));
}void GamePlay::initializeGL()
{
qglClearColor(Qt::green);}
void GamePlay::resizeGL(int width,int height)
{
glViewport(0,0,width,height);
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
GLfloat x = GLfloat(width) / height;
glFrustum(-x, x, -1.0, 1.0, 4.0, 15.0);
glMatrixMode(GL_MODELVIEW);
}
void GamePlay::paintGL()
{
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
draw();
}void GamePlay::draw()
{
glMatrixMode(GL_MODELVIEW);
glLoadIdentity();
glTranslatef(0,0,-10.0f);
glBegin(GL_TRIANGLES);
qglColor(Qt::red);
glVertex3f(-0.5f,-0.5f,0);
glVertex3f(0,-0.5f,0);
glVertex3f(0.5f,-0.5f,0);
glEnd();
}@ -
First strait OpenGL isn't trivial and isn't for most people, just knowing how to program in C/C++ and the OpenGL api isn't enough you need a background in advanced mathematics. Also if your doing things in the wrong order or if your not in the right mode at the correct time you will end up with a different result than what you expected. When programming in OpenGL you have to think of it in a procedural mind set. Post a link to your complete source code if you want help.