Changeset View

Standalone View

Context not available.
88	Q_SIGNALS:	88		Q_SIGNALS:
89		89
90	void activated(int);	90		void activated(int);
		91		void activatedStr(const QString&);
			sarsUnsubmitted Not Done one camelCase forgotten ;) sars: one camelCase forgotten ;)
			antonarnoldAuthorUnsubmitted Not Done oops :-) but I use this opportunity to ask a question I already had in mind. Is this a feasible way to pass the two overloaded signals? More equivalent to the QComboBox signals would be to use overloaded signals too. But in my opinion this may potentially cause much more follow up problems than introducing a distinct signal name. antonarnold: oops :-) but I use this opportunity to ask a question I already had in mind. Is this a feasible…
			sarsUnsubmitted Not Done It is a mater of taste, but in deed it is simpler to have distinct signal names in stead of overloads. Overloads need special handling to connect with the new connect style. sars: It is a mater of taste, but in deed it is simpler to have distinct signal names in stead of…
91		92
92	private:	93		private:
93	QComboBox *m_combo;	94		QComboBox *m_combo;
Context not available.