General and Desktop

@Bonnie ok. thanks

Thank you, I actually commented out the delete because I wasn't sure of the removeWidget behaviour, now it works flawlessly

Hi @SteMMo, I'm glad you figured it out. So please mark this topic as SOLVED too. Thanks!

@Asperamanca said in Future of QGraphicsView and QGraphicsScene: @jeremy_k said in Future of QGraphicsView and QGraphicsScene: @Asperamanca I think my point was missed. There's no need to choose Quick|Graphics View|Widgets for the entire application. Use each where they make sense and use the underlying Qt core functionality to communicate. Yes, I missed your point. But maybe you missed mine: There is currently no better technology (in Qt) for some use cases than GraphicsView. Of course I can mix and match, depending on what I need. No, I didn't. We're in agreement there. It's easy to look at the graphics silos and forget that they can cooperate.

I haven't used VideoWriter But from the documentation: cv::VideoWriter::VideoWriter ( const String & filename, int fourcc, double fps, Size frameSize, bool isColor = true ) Parameters isColor If it is not zero, the encoder will expect and encode color frames, otherwise it will work with grayscale frames. and virtual void cv::VideoWriter::write ( InputArray image ) Parameters image The written frame. In general, color images are expected in BGR format. Since you are writing grayscale images, I think you should pass 0 as isColor while currently you are using 1. Also I think this may be not quite related to Qt...Wouldn't it be better to find an OpenCV forum to ask this kind of questions? (Of course if the crash is due to the image conversion, then it is kind of Qt related.)

hi thx for answers @Christian-Ehrlicher said in access a signal of base class within the derived class: by re-defining the signal in the derived class yes, I accidentally redefined a signal with the same name in the derived class, that was the issue.

As I've solved my own question in https://forum.qt.io/post/614152 thread, I'm marking this one as solved.

So could anyone give some advice? :(

Okay, got it: Relevant code resides in QApplication and cannot be changed by subclassing QWidget. There’s no way around Qt::FocusPolicy but there is the possibility to add other attributes. Thanks a lot!

@oblivioncth said in Help with Autotest for Gerrit submission: So I should just add the cases locally, ensure they test correctly, and then commit --amend & push the changed test file as part of the rest of my submission? That's correct yes.

It might be an issue with macOS 10.15. One thing you can do as a workaround is to disable the native macOS menu bar. You will have it on the QMainWindow but it should be usable.

Hi, Shouldn't you rather post that on the GStreamer forum ?

@Daniel_Contro hi Good to hear. best to set this as solved and make a new one as then its easier for others to search :)

@RobbieP said in event connect not honoring default value of handler: Signal void QSpinBox::valueChanged(int i) --- and your connect() to QOverload<int>::of(&QSpinBox::valueChanged) ---sends i as parameter, you let that through to your slot void divisions1Changed(bool color = false) as the value of color. Change your slot to match, or munch the i parameter in a lambda.

Hi, You would need to implement a custom QStyledItemDelegate to scale the image.

gstreamer is installed or not? To be honest, I'm not remember. But I saw some info from the QtMM developers how to compile the GST backend on Windows. Or it was in developer mailing list, or somewhere in readme, I'm don't remember that, sorry. :( UPD: You can try to search also on this forum, e.g. you can read this topic or this topic.