You need to not be defining those pointers at the top, they don't do
anything and the syntax is weird. You should only have from the includes
down, and there is a good qt forum at

 

http://www.qtforum.org/

 

-John

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of benny porat
Sent: Thursday, November 16, 2006 11:36 AM
To: osg users
Subject: Re: [osg-users] GUI

 

ops, he did those error because I put this kine before the include,
I put them after and the error of before came back,
he write me:
undefined reference to `QString::shared_null'
[/usr/lib/qt3/include/qstring.h] 
undefined reference to `QStringData::deleteSelf()'
[/usr/lib/qt3/include/qstring.h] 
undefined reference to `QApplication::QApplication(int&, char**)'
main.cpp   
undefined reference to `QString::QString(char const*)'    main.cpp  
.
.
.

someone, undestand way? what shold I do to compile it in eclipse?



On 11/16/06, benny porat <[EMAIL PROTECTED]> wrote:

he is know give an error from the line I add, he wrote:
/main.cpp:10: error: expected constructor, destructor, or type
conversion before '*' token
../main.cpp:11: error: 'QString' does not name a type
../main.cpp:12: error: expected constructor, destructor, or type
conversion before '*' token
../main.cpp:13: error: expected constructor, destructor, or type
conversion before '*' token

for this prgoram:


/****************************************************************
**
** Qt tutorial 1
**
****************************************************************/


QApplication *qApp;
QString QString::null="";
QStringData *QString::shared_null=0;
QWidget *QApplication::main_widget = 0;

#include <qapplication.h>
#include <qpushbutton.h>


int main( int argc, char **argv )
{
    QApplication a( argc, argv );
    qApp = &a;
    
    QPushButton hello( "Hello world!", 0 );
    hello.resize( 100, 30 );

    a.setMainWidget( &hello );
    hello.show();
    return a.exec();
}

I think I dont understand you, what I do wrong?

thanks
NB

 

On 11/16/06, Dieter Pfeffer < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:

I had the same problems a time ago - try:

 

QApplication *qApp;

QString QString::null="";

QStringData *QString::shared_null=0;

QWidget *QApplication::main_widget = 0;

int main( int argc, char **argv )

{

 QApplication a( argc, argv );

qApp = &a;

....

 

 

 

Dieter

 

Unclassified Mail

-------------------------

 

        -----Original Message-----
        From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of benny porat
        Sent: Thursday, 16 November, 2006 15:49
        To: osg users
        Subject: Re: [osg-users] GUI

        I found this toturial

        http://doc.trolltech.com/3.3/tutorial1-01.html

        I try to compile it (I work with eclipse)

        and I get error that I dont understand what to do

        I gat error for every kine in the main:

        undefind reference to 'QString::shared_null....

        .

        .

        undefind reference to 'QApplication::QApplication(int&,char **)'

        ...

        and so on...

         

        I think that it something with the configure of the build?

        do you know what I need to do?

         

        thanks

        NB
         

        On 11/16/06, Robert Osfield <[EMAIL PROTECTED]> wrote: 

        Hi Garret,
        
        On 11/16/06, Garrett Potts <[EMAIL PROTECTED]> wrote: 
        > I am not sure of other peoples experiences.  The visualization
system I am
        > running based on OSG is very smooth on the Qt 4.1.4 version
but when I
        > upgraded to 4.2 and without changing a line of code and just
do a re-compile 
        > the scene became very Jerky.  Playing with Qt's timer interval
it became
        > better but never looked into it further.
        >
        > Not sure if this information is useful but I am also curious
if others have 
        > experienced similar problems.
        
        I haven't seen this, but it sounds like the timer has been given
a
        lower priority or simply implemented differently.
        
        Using GUI timers to drive redraws isn't ideal, for solid
framerates 
        you really need to run a separate graphics thread.  For any
serious
        vis-sim work this is essential.  For interactive apps GUI timers
will
        often suffice, but as you've found out you are at the mercy of
the
        Windowing toolkits implementation of its timers. 
        
        Robert.
        _______________________________________________
        osg-users mailing list
        [email protected]
        http://openscenegraph.net/mailman/listinfo/osg-users
        http://www.openscenegraph.org/

         


_______________________________________________
osg-users mailing list
[email protected] 
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/





 

_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to