Questions about zooming QGraphicsView

[JovianGhost]

Why not?

Well, I suppose the main reason is that I want to keep all GUI-related design in the GUI editor. If I subclass QGraphicsView, then I have to manually code instantiation and adding it where I want it. I know it doesn't sound like a big deal, and actually sounds pretty silly, but the way I see it part of the benfit of having a WYSIWYG GUI designer is that you don't have to worry about this stuff anymore. Guess I'm just spoiled.

Yes, by your view. That wouldn't be a problem if you would subclass your view. But as a workaround you can install an event filter on your view and handle the weel event there, or better do not handle it there so your function comes to play again.

Well, I guess that's as good of an argument as any to subclass QGraphicsView.
If only I had a nickel for every time I had to subclass an existing class to make one minor change...

PS It worked, thanks!

[Lykurg]

Well, I suppose the main reason is that I want to keep all GUI-related design in the GUI editor. If I subclass QGraphicsView, then I have to manually code instantiation and adding it where I want it. I know it doesn't sound like a big deal, and actually sounds pretty silly, but the way I see it part of the benfit of having a WYSIWYG GUI designer is that you don't have to worry about this stuff anymore. Guess I'm just spoiled.

First, I am fine that you don't want to subclass!
But I always wonder why people don't want to do so. As for your WYSIWYG argument: You can promote a widget in designer. So you can use your subclass and in designer it behaves like a normal graphics view and sets all properties correctly to your prometed subclass.