de10bf4955
In tst_QEvent, add a check that exhausts the available event type ids and verifies that registerEventTypes() returns -1 in that case, as documented. I haven't found a way to test the other case in which -1 is returned. Since this test operates on a global write-only registry the new test case needs to keep track of whether the earlier test cases have run successfully. If they didn't, skip this test case. Change-Id: I68ea9d17d10dcec22175994aba269dd09c9adf43 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> |
||
|---|---|---|
| .. | ||
| qbackingstore | ||
| qclipboard | ||
| qdrag | ||
| qevent | ||
| qfileopenevent | ||
| qguiapplication | ||
| qguieventdispatcher | ||
| qguieventloop | ||
| qguimetatype | ||
| qguitimer | ||
| qguivariant | ||
| qinputmethod | ||
| qkeysequence | ||
| qmouseevent | ||
| qmouseevent_modal | ||
| qpalette | ||
| qscreen | ||
| qsurfaceformat | ||
| qtouchevent | ||
| qwindow | ||
| kernel.pro | ||