Creating events instead of signals/slots
-
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.
-
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.
-
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.
-
[quote author="Revu" date="1301986907"]@Andre:Thank you for your response.Could you explain the same with a code snippet please.So that I can understand better.[/quote]
Not without knowing what your back end looks like and how to communicate with it, no. And to be honest, I don't think I can or want to do that even if you provided the needed code and documentation. I think the concept should be clear though?
-
I have multiple screens for a outgoing call like Idle,Dial,Progress and Connect screen.My backend controller program is in C.I need to change from Idle to Dial.After I enter the number show progress screen and finally connect screen after the call is established.Based on the events I get from C,my screen will change.Its like with button click I will wait for an event and then display the screen.While showing the other screen,am closing the current(using signal and slot mechanism).So how could I do that with events.
-
Now you are just asking the same question all over again. Sorry, but you really have to do your actual work yourself. Many people have already chimed in to try to help you, but if you just keep repeating your question, we're getting nowhere.
Perhaps a simple state machine is what you want? The different events from your backend could trigger state changes (read the documentation on QStateMachine before asking here how that works!) and your different states could determine what screen is visible.