Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support signals in introspection XML #23

Open
semafor opened this issue Jul 20, 2016 · 1 comment
Open

Support signals in introspection XML #23

semafor opened this issue Jul 20, 2016 · 1 comment

Comments

@semafor
Copy link
Contributor

semafor commented Jul 20, 2016

Looking at the code, and based on experiments, it does not look like dbusmock currently supports mocking pre-existing signals. It supports EmitSignals, but though I lack the appropriate terminology, it seems there are emitted signals and pre-existing signals?

E.g. using qt, connecting to a signal known to exist on an interface, I get:

QObject::connect: No such signal com::canonical::SystemImage::DownloadStarted() in …systemimage.cpp:99
@martinpitt
Copy link
Owner

The D-Bus specification just has "signals"; they all get emitted somewhere (that's the point of them), and otherwise behave pretty much like a method call without a return call/value.

What could happen there is that signals don't appear in the interface introspection XML, as they don't get declared? And whatever code you use may rely on that?

@martinpitt martinpitt changed the title Support mocking signals Support signals in introspection XML Jan 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants