Deploy a Library

[wysota]

You are creating a local QApplication object that goes out of scope immediately afterwards. The run() method doesn't make sense too - "if there is no qApp, call qApp".

[cafu1007]

HI Thanks for the answer i have fixed that in the code post that is how i am using it, but i got a warning "QApplication was not created in the main() thread.", and still does call the slot, i have tried also to decalre a as global pointer make new in the run but also do not work, sorry the previous mistake i was cutting and pasting.

[wysota]

So what's the problem now?

[cafu1007]

the problem is the same the slot are not being called

[cafu1007]

QApplication *a;
void Thread::run()
{
	qDebug("run");
 
	if (!a)
	{
		qDebug("no application running");
		int argc = 1;
		char *argv[] =
		{ "setup", NULL };
		a = new QApplication(argc, argv);
		QObject::connect(this, SIGNAL(Kill_me()), a, SLOT(quit()));
		qDebug("start running");
		a->exec();
		qDebug("application end");
	}
	else
	{
		QObject::connect(this, SIGNAL(Kill_me()), a, SLOT(quit()));
		qDebug("start running");
		a->exec();
		qDebug("application end");
	}
}
 
static ClassD *pToFunc;
Thread t;
dllExport int func1(void)
{
	if (!qApp)
	{
		qDebug("no application running");
		int argc = 1;
		char *argv[] =
		{ "setup", NULL };
		a = new QApplication(argc, argv);
	}
	qInstallMsgHandler(debugWinMsgHandler);
	t.start();
	t.setPriority(QThread::HighPriority);
	qDebug() << "func1";
 
	pToFunc = new ClassDl();
	return pToFunc->connectToServer("127.0.0.1", 9190);
}

QApplication *a;
void Thread::run()
{
	qDebug("run");

	if (!a)
	{
		qDebug("no application running");
		int argc = 1;
		char *argv[] =
		{ "setup", NULL };
		a = new QApplication(argc, argv);
		QObject::connect(this, SIGNAL(Kill_me()), a, SLOT(quit()));
		qDebug("start running");
		a->exec();
		qDebug("application end");
	}
	else
	{
		QObject::connect(this, SIGNAL(Kill_me()), a, SLOT(quit()));
		qDebug("start running");
		a->exec();
		qDebug("application end");
	}
}

static ClassD *pToFunc;
Thread t;
dllExport int func1(void)
{
	if (!qApp)
	{
		qDebug("no application running");
		int argc = 1;
		char *argv[] =
		{ "setup", NULL };
		a = new QApplication(argc, argv);
	}
	qInstallMsgHandler(debugWinMsgHandler);
	t.start();
	t.setPriority(QThread::HighPriority);
	qDebug() << "func1";

	pToFunc = new ClassDl();
	return pToFunc->connectToServer("127.0.0.1", 9190);
}

To copy to clipboard, switch view to plain text mode 

Like this work, i suppose cause of the priority of the thread the exec is called faster so when the function connect to server is called there is an application running, also i got this warning "QApplication::exec: Must be called from the main thread".

back to one question how can i assure that qApp is being executing?(tha the called to exec() was done).

Thanks

I am not calling the thread to start the Qapplication .exec(). Now it works. Is strange that there is a Qt application running, and the qApp is not recognized and a new one is created, as my understanding the QApllication shoul be a singlenton,isn´t it? the CCltClient is a thread and when a connect to server is called the thread is started. Is there no need to call qApp.exec() so it start to recognize the signals? i got a bit confused.

dllExport int func1(void)
{
	qInstallMsgHandler(debugWinMsgHandler);
	if (!qApp)
	{
		qDebug("no application running");
		int argc = 1;
		char *argv[] =
		{ "setup", NULL };
		a = new QApplication(argc, argv);
	}
	qDebug() << "func1";
	pToFunc = new ClassD();
	return pToFunc->connectToServer("127.0.0.1", 9190);
}

dllExport int func1(void)
{
	qInstallMsgHandler(debugWinMsgHandler);
	if (!qApp)
	{
		qDebug("no application running");
		int argc = 1;
		char *argv[] =
		{ "setup", NULL };
		a = new QApplication(argc, argv);
	}
	qDebug() << "func1";
	pToFunc = new ClassD();
	return pToFunc->connectToServer("127.0.0.1", 9190);
}

To copy to clipboard, switch view to plain text mode 

this is how it looks the func1 now.

[wysota]

Thread can't be a subclass of QThread, this doesn't make sense. If it is a subclass of QThread then call QThread::exec() instead of QApplication::exec() (and create the application object in the main thread then). Otherwise use native means to create a thread and try instantiating the application object there.

[cafu1007]

Sorry i do not understand. shall i leave the the last form of func1, but also call t.start() and in the run call exec(). and leave it running for the time tha the application need it. is this what you mean?.. and what about the singleton of QApplication, why a new one is created, or at least why is no reconigzed as exiting....

and as i said before i not calling any longer QApplication::exec(). but in the CCltClient in the run i call QThread::exec(). is this why it works?

A last QApplication *a should remain globlal so it does not go out of scope....

Thanks....

[wysota]

Sorry i do not understand. shall i leave the the last form of func1, but also call t.start() and in the run call exec(). and leave it running for the time tha the application need it. is this what you mean?..

You need an event loop. Qt doesn't care if it is going to be the main event loop (QApplication::exec()) or a per-thread loop (QThread::exec()) as long as there is something to process events. So choose either approach and stick with it.

and what about the singleton of QApplication, why a new one is created, or at least why is no reconigzed as exiting....

Application object is not created automatically. You have to create it yourself (reglardless if you intend to use a per-thread event loop or the main event loop -- the application object has to exist somewhere).

[cafu1007]

Application object is not created automatically. You have to create it yourself (reglardless if you intend to use a per-thread event loop or the main event loop -- the application object has to exist somewhere).

Yeah but there a Qt Gui running so it should somewhere in the system or i am wrong

[wysota]

You said it was an MFC app. Now I'm confused.

[cafu1007]

yeah mfc app is using the dll that i have show the code. but in the same system there is also a gui appliction which was developed using Qt and QWidgets...

[wysota]

Each application needs its own application object.