googleid_117965
13 years agoNew Contributor
No access to public Qt methods
Hi everybody,
I have a Qt application that's debug compiled with the MSVC2008 compiler through Qt Creator. TestComplete displays the 'open application' logo next to the process and it's able to see all the application's controls. However, it doesn't seem to be able to access the public methods defined in any of these GUI classes. For example, the application has a custom widget that inherits from QWidget and has public methods like this:
class CustomWidget : public QWidget
{
Q_OBJECT
public:
bool isOpen() const;
void setOpen(bool open);
[...]
}
These methods are not shown in the object browser or object spy. On the other hand, public properties that are defined with the Q_PROPERTY macro are visible to TestComplete and can be accessed without any problems.
I tried compiling the application with Qt 4.8.0, Qt 4.8.1, Qt 4.8.4, different compiler flags (using qmake arguments) aswell as playing around with various TestComplete settings -- all to no avail. Does anyone have an idea what else might be the problem here?
Thanks in advance,
Nik
I have a Qt application that's debug compiled with the MSVC2008 compiler through Qt Creator. TestComplete displays the 'open application' logo next to the process and it's able to see all the application's controls. However, it doesn't seem to be able to access the public methods defined in any of these GUI classes. For example, the application has a custom widget that inherits from QWidget and has public methods like this:
class CustomWidget : public QWidget
{
Q_OBJECT
public:
bool isOpen() const;
void setOpen(bool open);
[...]
}
These methods are not shown in the object browser or object spy. On the other hand, public properties that are defined with the Q_PROPERTY macro are visible to TestComplete and can be accessed without any problems.
I tried compiling the application with Qt 4.8.0, Qt 4.8.1, Qt 4.8.4, different compiler flags (using qmake arguments) aswell as playing around with various TestComplete settings -- all to no avail. Does anyone have an idea what else might be the problem here?
Thanks in advance,
Nik