Closed kaamui closed 1 year ago
I only see the keyReleaseEvent
, not the keyPressEvent
. Will investigate further.
Just uncomment it again and change it to
QApplication::sendEvent (scene().get(), event);
and it works again!
... sorry to have bothered you for this. I just don't know why it was commented. I don't remember at all having done that
Probably a wrong manipulation. Thank you for your help.
I only see the
keyReleaseEvent
, not thekeyPressEvent
. Will investigate further.
I must have gone too fast in my tests and confused the different calls... very sorry to have bothered you with such stupid things. I try to only ask for your help when there is a question of technical interest.
... I just had a 4-day weekend and I found a way to chain the nonsense where I'm supposed to be in great shape to work... :smile:
... I just had a 4-day weekend and I found a way to chain the nonsense where I'm supposed to be in great shape to work... smile
Hehe :) And never mind. I know such things can happen. Once at work I started to implement a new feature, and when I was close to be ready I found out that I had a branch where I already did this two months ago. Just didn't remember. Such things just happen.
That's quite a big regression I was not expecting...
I did a git bisect and it seems related to the changes we did in UBGraphicsScene's ownership, as no issue at this point of the branch : 4f49a2fa, and appears at the first commit that compiles after.
QGraphicsScene::keyPressEvent is correctly called, QGraphicsTextItem::keyPressEvent too, so I don't understand what's happening.
I did reproduce it in a macOS and my Linux laptop.
I thought it could be that the scene we're trying to send key press events to is not the good one, but it is the same scene all over the place ...
Do you see something that could explain this ? I could not find any related issue in the Qt bug tracker.