Hi Kevin! All signals are protected. A "private" or "public" section atop of it does not effect this. So the signals are available to others.
Best Regards, Tobias ________________________________________ From: [email protected] [[email protected]] On Behalf Of Wangbing Kevin (Nokia-MS/Beijing) Sent: Friday, August 20, 2010 8:16 AM To: [email protected] Subject: [Qt-creator] Why not open the signals in Utils::PathChooser class Hi, I need a widget that can provide 2 accesses to specify a file path: user can input the file path directly or browse all files then select one. In addition, that widget can validate the file path and sent relative signals to other widgets. I find the Utils::PathChooser class satisfy my needs except sending signal. The declaration of Utils::PathChooser reserve the signals for itself rather than open them. qt-creator/src/libs/utils/pathchooser.h ======================================================== …………… private: …………… signals: void validChanged(); void validChanged(bool validState); void changed(const QString &text); void editingFinished(); void beforeBrowsing(); void browsingFinished(); void returnPressed(); …………… ======================================================== I think Utils::PathChooser is very valuable in specifying file path scene, and the validChanged() signal is the key to link the widget to others. So I suggest that opening the signals in Utils::PathChooser class to extend the using scope. B.R. Kevin Wang _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
