General and Desktop

Hello everyone, I am actually experiencing the exact same issue, using Qt 5.15.2, on Win 10. I have tried with *.webm and *.mp4 videos. Tried using both : QMediaPlaylist::Loop QMediaPlaylist::CurrentItemInLoop Both give the same "split second blackout" glitch. Hope this helps. Regards,

@Publicnamer It is recommended that you check https://doc.qt.io/qt-5.15/qtablewidget-members.html where all the methods and signals of QTableWidget are (together with the base classes)

@Publicnamer QTreeWidget or QTreeView.

The font for a cell can be changed by returning the desired font for Qt::FontRole which you can set in your item via QTableWidgetItem::setFont().

@Audetto please provide a minimal and reproducible example

@Sussybaka What about it? That post is complaining that the Qt installer did not repair a broken Microsoft runtime installation on Windows. Your original post make no mention of Qt and you are not running on Windows (just a partial imitation of one).

@Publicnamer Well MOC runs on the .h files included in the project so if you didn't include the header file in the .pro file, then MOC would have no idea it has to process it.

Hi and welcome to devnet, Why not parse that external data at the start of your application to build the data for your completer ?

Hi, No, you either have to cross-compile it yourself or if your target is powerful enough, build directly on it with the Qt provided by the Linux distribution that runs on jt.

Hi, @Publicnamer said in Open-file dialog returning gibberish?: const char *path = filename.toStdString().c_str(); You are keeping the address of a temporary std::string that you convert to a c string. So there's a high chance that path points to garbage memory.

@SilentWolf use layouts

@mrjj THANK YOU :)) Helped a lot!

Just for information, the "weird behavior" is UTF-8 decoding/encoding. These bytes { 0x0c, 0xa6, 0xd5, 0x00, 0x02, 0x08 } do not represent a valid UTF-8 encoded string. When readLine() attempts to decode the byte as a UTF-8 string it gets to the invalid portions, specifically the bytes 0xa6, 0xd5, and decodes them as the Unicode Replacement Character 0xfffd. This flags the invalidity without throwing an exception, and makes the subsequent string safe to handle. If you then explicitly UTF-8 encode the string containing U+FFFD characters then they get correctly encoded as UTF-8 0xef, 0xbf, 0xbd.

Yes and it's all in the main thread now.

Hi, Out of curiosity, why do you need QSharedPointer in this case ?

See https://code.qt.io/cgit/qt/qtopcua.git/tree/examples/opcua

@VRonin said in KDE Frameworks KSyntaxHighlighting; docs?: @Ewan-Green said in KDE Frameworks KSyntaxHighlighting; docs?: It's not quite the extensive documentation of every member like I'm used to with Qt. You can find it here. Qt spoils us with the quality of the documentation but if, on that page, you click on Class List you can find the documentation class-by-class and method-by-method Thank god! I was looking for exactly this. Thank you.

To continue the same way as @JonB I think the reason is that C++ is not a dynamic language as objectiveC or Java, foreach(Base* widget, vector) / I hate auto !!! { widget->handleSomething(); } Here C++ see widget is a Base instance and when the compiler looks at the handle method, it sees it as protected and stop at it with an error. C++ is not so smart :)

Hey guys, Thanks a bunch, in all i wanted to understand the insertRows and insertRow, plus how to implement it. You guys directed me in right direction Thank You. marking resolved