Hey Sven, > Problem: The method update() has to be called each update to emit a existing > signal. The virtual method WApplication::notify(..) is called less frequent > and therefore not suitable.
notify() is called for every event though... It is not clear to me what you are really wanting to do... for example, I cannot understand why you are creating a new signal for each event: a signal is usually something which you want to keep around as long as its parent widget, and attach (and remove) listeners to. Perhaps you do not need a signal at all. A signal is typically needed if you want to be able to make a widget produce an event to which other parts of your application (of which that widget does not know the existence) may react (signals and slots are glorified callback mechanisms). In your case, it seems that Application is the only user of the widget it creates itself, and thus the widget is not really a necessary part of the solution. Regards, koen ------------------------------------------------------------------------------ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
