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

No QTimer "timeOut" signal available for Qt5 #629

Closed
klayoutmatthias opened this issue Aug 20, 2020 · 0 comments
Closed

No QTimer "timeOut" signal available for Qt5 #629

klayoutmatthias opened this issue Aug 20, 2020 · 0 comments
Assignees
Labels

Comments

@klayoutmatthias
Copy link
Collaborator

klayoutmatthias commented Aug 20, 2020

See https://www.klayout.de/forum/discussion/1624/qtimer-misses-timeout-signal#latest for the discussion and for a workaround.

Technically the reason is that Qt5 introduced "private signals" which are not captured correctly by KLayout's Qt binding.

@klayoutmatthias klayoutmatthias self-assigned this Aug 20, 2020
klayoutmatthias added a commit that referenced this issue Aug 21, 2020
In addition, the "destroyed" and "objectNameChanged" signals
were added (specifically to QObject).

The API binding for Qt5 was updated which adds some events.
klayoutmatthias added a commit that referenced this issue Sep 14, 2020
In addition, the "destroyed" and "objectNameChanged" signals
were added (specifically to QObject).

The API binding for Qt5 was updated which adds some events.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant