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.

Sign up for GitHub

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

Jump to bottom

Teach App4Test how to understand WM_CLOSE #15

Open
jcfr opened this issue Apr 8, 2012 · 0 comments
Open

Teach App4Test how to understand WM_CLOSE #15

jcfr opened this issue Apr 8, 2012 · 0 comments

Comments

@jcfr
Copy link
Member

jcfr commented Apr 8, 2012

On windows, the --launcher-timeout test is currently disabled . Indeed, in that case, the function QProcess::terminate() sends a WM_CLOSE event and our App4Test doesn't handle it.

It may be possible to use SetConsoleCtrlHandler
jcfr added a commit to jcfr/AppLauncher that referenced this issue Apr 8, 2012
@jcfr
On windows - Disable '--launcher-timeout' test. See commontk#15
df0b995 
* This is motivated by the fact App4Test does not understand WM_CLOSE.
jcfr added a commit that referenced this issue Apr 8, 2012
@jcfr
Merge branch '15-teach-app4test-wm-close'
556ced0 
* 15-teach-app4test-wm-close:
  On windows - Disable '--launcher-timeout' test.  See #15
@jcfr jcfr removed the Todo label Jul 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcfr