Creating events instead of signals/slots

Revu

@Geroif:Hi..Yes close does its job.The problem is that am using static to raise my other window.I want to activate my next window before I close my current window.Always the next window will be event dependent to change to the next screen.
like I want to navigate between the screens initially from Idle screen to Dial screen.After I dial the number the number and press dial button I should show Progress Screen and finally Connect Screen after the call has been established.

Revu

Whether I could pass the events between two widgets/windows?Can you tell me how to do it?There is no mush details regarding QCloseEvent in the documentation.

andre

In his first reply, Gerolf already told you how to use custom events. -It doesn't matter much if you want to post your own event or a Qt event.- A QCloseEvent is just a subclass of QEvent that does not add any special members or methods.

I am not sure if posting your own QCloseEvent is going to work, since the spontaneous flag would be false. AFAIK, there is no public API to manipulate that flag, and I don't know if it would affect the handling of the event.

Edit: it turns out it does matter what kind of event you post.

giesbert

[quote author="Andre" date="1301564768"]In his first reply, Gerolf already told you how to use custom events. It doesn't matter much if you want to post your own event or a Qt event. A QCloseEvent is just a subclass of QEvent that does not add any special members or methods.
[/quote]
I thinnk it will not. QCloseEvent is also a reaction on the close() slot (if close is no reaction to a system close event, there is an if in the code for that) :-).

Sending a QCloseEvent will NOT close the widget!

@
... QWidget::event()
{
...
case QEvent::Close:
closeEvent((QCloseEvent *)event);
break;
...
}

void QWidget::closeEvent(QCloseEvent *event)
{
event->accept();
}
@

[quote author="Andre" date="1301564768"]
I am not sure if posting your own QCloseEvent is going to work, since the spontaneous flag would be false. AFAIK, there is no public API to manipulate that flag, and I don't know if it would affect the handling of the event.
[/quote]

It's totaly internal, I was trying to use it once... Did not work. Needed it for a virtual key board.

Revu

Do I have a solution to close a widget from another widget of different classes using events?How could I do that?

giesbert

As you need the widget pointer for sending events, you can just call close() method also. And it does the job. So why bother about sending events? Dou you need it asynchronous? Use QmetaObject::invokeMethod(...) with the queued invokation.

Revu

It should be synchronous with the close of the current widget and raise of other widget.

giesbert

Then call

@
widget2()->show();
widget2()->raise();
widget1()->close();
@

Revu

I had already used it in my program and its working.My question is that can't we do the same by passing events between those widgets.in examples given in qt4,in mainwindows there is a sample program named application in which the QCloseEvent has been used but am not able take that and implement to my requirement.It throws a compile error as
@/usr/include/qt4/QtGui/qwidget.h:84: error: forward declaration of ‘struct QCloseEvent’
@

Help me.

giesbert

you should add the include for the QCloseEvent, it's only forward declared!

@
#include <QtGui/QCloseEvent>
@

It's staed in the error message...

Revu

Thank You.That is clear now.How could I pass the event between two different widgets.Suppose if I had implementted the QCloseEvent in MainWindow then how to call that from my SubWindow?

giesbert

to forward events to a parent, you can just use event->ignore() which should then send the take care that it is also send to the parent (don't know if that also happens to a CloseEvent).

Revu

Well!I have multiple screens.I need to display a particular screen based on the event I pass from my first screen.With signal and slot,I need to write those lines of code in all the files.Suppose if I have some 20 screens then by passing an event from my first screen I should display 10th(or 15th whatever) or close that particular window by having all my control in my first screen.

goetz

Then connect your signals to a slot/some slots in the first screen.

Revu

@Volker:I had done that earlier.How well can I organise these so as to have the control to close my other windows?Just like as we have goto in C.

goetz

It's the same task as if you had events dropping in.

EDIT:
And as C++ is a superset of C, you have goto - if you really want to use this.

Revu

Can I traverse from 1st MainWindow to some 15th MainWindow that I have in my application?How well can I do this with signals?

andre

What do you mean with "traverse"? Call each of them in sequence?

Of course you can do this. Qt does it all the time. Slots are invoked in the order the connections are created, so that would also "traverse".

Revu

The GUI should respond depending upon the event received from the C running as back-end.

andre

OK, here's what I would do, and then I think I'll quit responding to this thread.

I would create a single QObject that is responsible for the communication with the C-based backend. This object receives the call-backs or events or whatever you call them from the backend, and emits corresponding signals for these events. The different windows connect to this object's signals to learn about the data they are interested in.