General and Desktop

@Abderrahmene_Rayene Thanks for your reply. In the end, I used CustomiDelegate, and the stylesheet of the table usually needs to be added with " "QTableWidget::item { padding:1px; }QTableWidget { gridline-color: #303030; }" class CustomDelegate : public QStyledItemDelegate { public: CustomDelegate(QObject* parent = nullptr) : QStyledItemDelegate(parent) {} void paint(QPainter* painter, const QStyleOptionViewItem& option, const QModelIndex& index) const override { painter->setPen(QColor(0x303030)); if (index.row() == 0) painter->drawLine(option.rect.topLeft(), option.rect.topRight()); if (index.column() == 0) painter->drawLine(option.rect.topLeft(), option.rect.bottomLeft()); QStyledItemDelegate::paint(painter, option, index); } };

@sierdzio Thank you very much, I fond it in"Archive".

@dan1973 hi, Isn't that because you set a range of 0 to 600 ?

Posting here just in case someone comes across this -- I ~think~ I found the solution to be related to app nap, originally discovered here. My application was in python, so I was able to use appnope to ensure my python application wasn't throttled & this solved my manifestation of this problem.

@Qt-embedded-developer then share a minimal compilable example that shows your issue.

@ChrisW67 Seemed to have found the solution!! The key was found here -- macOS was throttling with App Nap. Solved by installing appnope, and including import appnope appnope.nope() at the top of any PyQt application.

Hi, Thanks for sharing. You might find these links useful, they contain more information about this: Qt Widgets Examples — Translucent Background Frameless and transparent window

@sonichy What is your actual question/problem? If you have a list of numbers (integers or floats) and you want to save it to settings as a string and restore it as a list of numbers, and for some reason you don't want to do it via a QVariant like @ChrisW67 suggested, (is that what you want?) you need to: To save, you need to iterate the list calling QString::number() on each one to build up a comma (or other character)-separated string, then pass that to settings. To restore, you need to call QString.split() to split the string into items and call QString::toInt/Float() on each one to convert back to numbers. Of course, if you have the numbers stored as a separated string in your text edit or elsewhere and you only want to deal with that then you don't need to do joining/splitting/converting from/to numbers. UPDATE @sonichy said in How to change QVector to QString: @mpergand I accept your code You have gone back and changed your post to say "I accept your code" now, maybe you mean you have no problem, I don't know.

@hskoglund I just tested your proposal, but unfortunately it didn't work. I also tried without any wildcards and just wrote out one of the names and that didn't work either. I'm beginning to suspect that fromPath doesn't work with resources but I can't find any proof that it shouldn't

@MoonBrid said in QPushButton cannot be released: @JonB If I don't use processEvents(), that causes another problem. The program will block in the while loop, and the interface will become unresponsive, unable to press the button_2. Sorry, I give up. That is not what I asked you. I have asked/suggested more than once that you remove the processEvents() and then tell us whether the behaviour of holding the button down during the 2 seconds and then releasing it afterwards does or does not recognise the button up. That is all you had to try. I don't understand why it's so difficult to try something while you diagnose. No more from me now.

@FalsinSoft SORRY I AM not using qt6

Hi, Where do you have that library on your build machine ?

@EricR anything that is not a explicitly allocated on the heap is on the stack. Make lineSeries a pointer and allocated it using new in the constructor.

@SGaist Great!! Thanks!!

A custom item delegate might be required.

What the... ok, in case anyone ever runs into this. This is caused by compiling Qt 6.4.2 without harfbuzz. Why? Don't ask me.

Coincidentally, today my colleague sent me a Google paper about memory safety in C++: https://research.google/pubs/secure-by-design-googles-perspective-on-memory-safety/

@Pl45m4 Thanks!!!!