ignore shift to move between edit text
-
@rest
At some level I think you're telling us that your bar code scanner generates key events for the characters it meets?...I guess SHIFT itself raises a
CWidget::keyPressEvent? So (given what you're doing), you better make yourkeyPressEventcode look to see if its the SHIFT key and not do the focus swap in that case. Your focus swap code is what is causing it to act like TAB.I suspect apart from that that your approach is wrong, but the above is to answer your question as to why it behaves as it does..
-
Hi
Did you use debugger and check what key combination that makes it
"tab" to next edit ?
I wondering if the jump happens when u pass the key to
ui->leInformation->KeyPressEvent(event);
(then we can maybe do different, like remove shift) -
Hi
Did you use debugger and check what key combination that makes it
"tab" to next edit ?
I wondering if the jump happens when u pass the key to
ui->leInformation->KeyPressEvent(event);
(then we can maybe do different, like remove shift) -
@mrjj i will make some debugging now, but is not about that cause i commented ui->leInformation->KeyPressEvent(event); and is the same
@rest
if you dont forward the keys at all , it still jumps ?
Ok, it sounds like the input trigger key navigation.I assume you are using an USB scanner in hid keyboard mode.
You might want to install event filter on Application to find out what is going on.
http://doc.qt.io/qt-5/qobject.html#installEventFilterIts hard to suggest what to do when we dont really know why input makes it focus next control.
-
but witch one of the variables gets me the key pressed? i tried something like this !event->key() == Qt::ShiftModifier and doesnt work, there is another way to check?
@rest said in ignore shift to move between edit text:
Qt::ShiftModifier
if(event->modifiers() & Qt::ShiftModifier){...}
-
@rest
Be careful: I'm thinking you will get one event for just the SHIFT press, and thenQt::ShiftModifierwill also still be true for the event which arrives for theB.I don't get the whole intention of what you're trying to achieve with your code. You decide where input is to go based on:
if(focusWidget() == ui->lePath && !ui->lePath->text().isEmpty())Why? What's the logic here? What's the idea of switching focus here?
-
@rest
Be careful: I'm thinking you will get one event for just the SHIFT press, and thenQt::ShiftModifierwill also still be true for the event which arrives for theB.I don't get the whole intention of what you're trying to achieve with your code. You decide where input is to go based on:
if(focusWidget() == ui->lePath && !ui->lePath->text().isEmpty())Why? What's the logic here? What's the idea of switching focus here?
@JonB if i scanned a barcode means that focus is on first edit and he is not empty means i should change focus on second edit for scanning there, this is what i thought i don t have so much experience on this i don t really know how i can make this work
-
@JonB if i scanned a barcode means that focus is on first edit and he is not empty means i should change focus on second edit for scanning there, this is what i thought i don t have so much experience on this i don t really know how i can make this work
-
@JonB if i scanned a barcode means that focus is on first edit and he is not empty means i should change focus on second edit for scanning there, this is what i thought i don t have so much experience on this i don t really know how i can make this work
-
@rest
But aren't you saying the "key presses for the barcode" are for each letter? When the second key arrives inlePath(it has the focus, and it's no longer empty), won't your code send it toleInformation? -
You can try to use only click focus and not strong focus.
)
