Should I check QEvent dynamic_cast result if I already checked event->type()?
up vote
0
down vote
favorite
QEvent has a type() member function which returns the event type as enum value. Should I check dynamic_cast result for QEvent* if I already checked event->type(). E.g.
bool ClassName::eventFilter(QObject* obj, QEvent* event)
{
if (event->type() == QEvent::KeyPress)
{
auto ke = dynamic_cast<QKeyEvent*>(event);
if (ke) // <----------- needed?
{
// ...
}
}
// ...
}
Is if (ke) condition needed here?
c++ qt qevent
asked Nov 21 at 14:09
älёxölüt
1,86511446
add a comment |
up vote
0
down vote
favorite
QEvent has a type() member function which returns the event type as enum value. Should I check dynamic_cast result for QEvent* if I already checked event->type(). E.g.
bool ClassName::eventFilter(QObject* obj, QEvent* event)
{
if (event->type() == QEvent::KeyPress)
{
auto ke = dynamic_cast<QKeyEvent*>(event);
if (ke) // <----------- needed?
{
// ...
}
}
// ...
}
Is if (ke) condition needed here?
c++ qt qevent
asked Nov 21 at 14:09
älёxölüt
1,86511446
1
If you already know the type you can safely usestatic_castinstead without checking the result against null pointer. This is faster approach.
– vahancho
Nov 21 at 14:17
@vahancho hence second checking is redundant, right?
– älёxölüt
Nov 21 at 14:24
1
That's what I meant. Andstatic_castis more preferable in this case.
– vahancho
Nov 21 at 14:29
@vahancho maybe some reference to Qt documentation/implementation? Such info should be placed in answer area and accepted :)
– älёxölüt
Nov 21 at 14:34
Have a look at Qt doc.: Event Filters. There you find an example which uses astatic_castlike mentioned by @vahancho.
– Scheff
Nov 21 at 15:16
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
QEvent has a type() member function which returns the event type as enum value. Should I check dynamic_cast result for QEvent* if I already checked event->type(). E.g.
bool ClassName::eventFilter(QObject* obj, QEvent* event)
{
if (event->type() == QEvent::KeyPress)
{
auto ke = dynamic_cast<QKeyEvent*>(event);
if (ke) // <----------- needed?
{
// ...
}
}
// ...
}
Is if (ke) condition needed here?
c++ qt qevent
asked Nov 21 at 14:09
älёxölüt
1,86511446
QEvent has a type() member function which returns the event type as enum value. Should I check dynamic_cast result for QEvent* if I already checked event->type(). E.g.
bool ClassName::eventFilter(QObject* obj, QEvent* event)
{
if (event->type() == QEvent::KeyPress)
{
auto ke = dynamic_cast<QKeyEvent*>(event);
if (ke) // <----------- needed?
{
// ...
}
}
// ...
}
Is if (ke) condition needed here?
c++ qt qevent
c++ qt qevent
asked Nov 21 at 14:09
älёxölüt
1,86511446
asked Nov 21 at 14:09
älёxölüt
1,86511446
asked Nov 21 at 14:09
älёxölüt
1,86511446
asked Nov 21 at 14:09
älёxölüt
1,86511446
asked Nov 21 at 14:09
älёxölüt
1,86511446
1,86511446
1
If you already know the type you can safely usestatic_castinstead without checking the result against null pointer. This is faster approach.
– vahancho
Nov 21 at 14:17
@vahancho hence second checking is redundant, right?
– älёxölüt
Nov 21 at 14:24
1
That's what I meant. Andstatic_castis more preferable in this case.
– vahancho
Nov 21 at 14:29
@vahancho maybe some reference to Qt documentation/implementation? Such info should be placed in answer area and accepted :)
– älёxölüt
Nov 21 at 14:34
Have a look at Qt doc.: Event Filters. There you find an example which uses astatic_castlike mentioned by @vahancho.
– Scheff
Nov 21 at 15:16
add a comment |
1
If you already know the type you can safely usestatic_castinstead without checking the result against null pointer. This is faster approach.
– vahancho
Nov 21 at 14:17
@vahancho hence second checking is redundant, right?
– älёxölüt
Nov 21 at 14:24
1
That's what I meant. Andstatic_castis more preferable in this case.
– vahancho
Nov 21 at 14:29
@vahancho maybe some reference to Qt documentation/implementation? Such info should be placed in answer area and accepted :)
– älёxölüt
Nov 21 at 14:34
Have a look at Qt doc.: Event Filters. There you find an example which uses astatic_castlike mentioned by @vahancho.
– Scheff
Nov 21 at 15:16
1
1
If you already know the type you can safely use
static_cast instead without checking the result against null pointer. This is faster approach.– vahancho
Nov 21 at 14:17
If you already know the type you can safely use
static_cast instead without checking the result against null pointer. This is faster approach.– vahancho
Nov 21 at 14:17
@vahancho hence second checking is redundant, right?
– älёxölüt
Nov 21 at 14:24
@vahancho hence second checking is redundant, right?
– älёxölüt
Nov 21 at 14:24
1
1
That's what I meant. And
static_cast is more preferable in this case.– vahancho
Nov 21 at 14:29
That's what I meant. And
static_cast is more preferable in this case.– vahancho
Nov 21 at 14:29
@vahancho maybe some reference to Qt documentation/implementation? Such info should be placed in answer area and accepted :)
– älёxölüt
Nov 21 at 14:34
@vahancho maybe some reference to Qt documentation/implementation? Such info should be placed in answer area and accepted :)
– älёxölüt
Nov 21 at 14:34
Have a look at Qt doc.: Event Filters. There you find an example which uses a
static_cast like mentioned by @vahancho.– Scheff
Nov 21 at 15:16
Have a look at Qt doc.: Event Filters. There you find an example which uses a
static_cast like mentioned by @vahancho.– Scheff
Nov 21 at 15:16
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413913%2fshould-i-check-qevent-dynamic-cast-result-if-i-already-checked-event-type%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
If you already know the type you can safely use
static_castinstead without checking the result against null pointer. This is faster approach.– vahancho
Nov 21 at 14:17
@vahancho hence second checking is redundant, right?
– älёxölüt
Nov 21 at 14:24
1
That's what I meant. And
static_castis more preferable in this case.– vahancho
Nov 21 at 14:29
@vahancho maybe some reference to Qt documentation/implementation? Such info should be placed in answer area and accepted :)
– älёxölüt
Nov 21 at 14:34
Have a look at Qt doc.: Event Filters. There you find an example which uses a
static_castlike mentioned by @vahancho.– Scheff
Nov 21 at 15:16