You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tdesdk/kspy
Michele Calgaro d3656a49e6
Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines
11 months ago
..
CMakeL10n.txt Add CMakeL10n rules. 6 years ago
CMakeLists.txt [tdesdk/cmake] added forgotten files 13 years ago
Makefile.am Renaming of files in preparation for code style tools. 4 years ago
README Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. 15 years ago
classinfoview.cpp Replace tqt_mo_* defines 1 year ago
classinfoview.h Replace Q_OBJECT with TQ_OBJECT 1 year ago
kspy.h Removed code formatting modelines. 4 years ago
main.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
navview.cpp Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines 11 months ago
navview.h Replace Q_OBJECT with TQ_OBJECT 1 year ago
navviewitem.cpp Rename a number of classes to enhance compatibility with KDE4 12 years ago
navviewitem.h Rename a number of classes to enhance compatibility with KDE4 12 years ago
propsview.cpp Drop USE_TQT4 code 1 year ago
propsview.h Replace Q_OBJECT with TQ_OBJECT 1 year ago
receiversview.cpp Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines 11 months ago
receiversview.h Replace Q_OBJECT with TQ_OBJECT 1 year ago
sigslotview.cpp Rename additional header files to avoid conflicts with KDE4 12 years ago
sigslotview.h Replace Q_OBJECT with TQ_OBJECT 1 year ago
spy.cpp Use new TQ_METHOD, TQ_SIGNAL, TQ_SLOT defines 11 months ago
spy.h Replace Q_OBJECT with TQ_OBJECT 1 year ago

README

KSpy
====

KSpy is a utility intended to help developers examine the internal
state of a Qt/KDE application. KSpy graphically displays all the
QObjects in use, and allows you to browse their properties. Using KSpy
is very simple, include kspy.h and call KSpy::invoke() when you want
to looks inside your app. The KSpy function is inline and the main
part of KSpy is dynamically loaded, so you may even want to leave this
in the release build of an application.

Richard Moore, <rich@kde.org>