@J.Hilk said in Delete All Files: Remove-Item "C:\path\to\folder" -Recurse -Force It's working, Thank you.. void delete() { const QString appDir = QDir::toNativeSeparators(QCoreApplication::applicationDirPath()); const QString ps = QString( "Start-Sleep -Seconds 2; " "Remove-Item -LiteralPath \"%1\" -Recurse -Force" ).arg(appDir); QString program = "powershell.exe"; QStringList args = { "-NoProfile", "-ExecutionPolicy", "Bypass", "-WindowStyle", "Hidden", "-Command", ps }; const QString workingDir = QDir::tempPath(); qint64 pid = 0; const bool ok = QProcess::startDetached(program, args, workingDir, &pid); if (!ok) { return; } QTimer::singleShot(0, qApp, &QCoreApplication::quit); }

@ChrisW67 Thank you! Yes, I thought about smart pointers as well but I am (yet) not very familiar with it and don't know which one is correct. Currently we work most of the time with raw pointers and the old Qt3 QPtrList . Maybe the qt-version: https://forum.qt.io/topic/19073/any-difference-between-std-shared_ptr-and-qsharedpointer/2 could be an option as well...

@Christian-Ehrlicher Great, Thank you!

Ok thanks! I think I understand what I have to do

@SpaceToon said in Check if a pointer was deleted in Qt for GUI Application: Thank you very much, that worked! Do you mean just replacing delete with deleteLater()? It would be discoveryAgent->deleteLater(); Check out the documentation under the given link in my post.

Olá @Seph123. Infelizmente essa funcionalidade não está diretamente disponível para nós. Eu recomendo que você encaminhe um e-mail para qtaccount@qt.io.

@mpergand Thank you for help.

@koahnig thank you.

Thank you @mrjj I will go ahead and mark this as solved then. I know my IP Editor isn't exactly elegant, but with the requirements I'm given and the restrictions, I've done the best I can.

@mrjj I've changed it to check if it's in the first edit, to stop the timer so it'd look like 123.___.___.___ And then the user will have to manually hit "Delete" repeatedly to delete the characters. This way, the program doesn't crash. It's not exactly elegant, but it's close enough to the requirements I was given. I have also changed that curEdit->installEventFilter(this) is only called once. Thank you very much for your help, I will go ahead and mark this as solved.

No, it doesn't. The QLayoutItem is not the parent of the widget, it is not a QObject. That's not its job.

@kishore_hemmady said in QListWidget delete selected item: how can i achieve this by selecting the check Box rather than selecting the list content? for(int i=ui->listWidget->model()->rowCount()-1;i>=0;--i){ if(ui->listWidget->model()->index(i,0).data(Qt::CheckStateRole).toInt()==Qt::Checked) ui->listWidgetMy->model()->removeRow(i); }

@Keyos I meet the same problem,and when i launch my app,the memory usage become 50% even the dialog is not actived,maybe the next release will be better.

I've found the problem it is a process deleted without initialized.

That wasn't really clear from your original description. In that case, use a filter. QSortFilterProxyModel for example

@panosk Thanks it works :) Henrik

However I did certainly what you said that was only little part. Thank for your answer, without it I would only find a way around this issue probably. (like 2 parallel QLists) So what works? I make additional QObject with parent "this (list of lists)". Then I make it parent of every QObject I want to delete (QObjects with list and QObjects within lists). I don't change CppOwnership. After that I clear() list and add new QObjects (obsolete QObjects stay accessible as children of that additional QObject). After final emit I delete that QObject with deleteLater(). QPointer isn't necessary here I think. I tried deleteLater in another way of doing things and it crashed, so that is the only way I found. My application deletes QObject and all children with it. With neither crash or leak. QObject * delQObject = new QObject (this); set_parents_list(delQObject ); m_list_of_listQobjects.clear(); for () m_list_of_listQobjects.append(new listQobject); emit m_list_of_listQobjectsChanged(m_list_of_listQobjects()); delQObject->deleteLater(); where: listoflistsofQObjects :: set_parents_list(QObject * parent) { for (int i = m_list_of_listQobjects.count(); i>0; i--) { m_list_of_listQobjects[i-1]->setParent(parent); m_list_of_listQobjects[i-1]->set_parents_list(parent); } } Following function isn't necessary if QObjects already have parent that is deleted (like listofQObjects or some QObject inside it). It's safer to make elements children, because then one doesn't need to call deletes in destructor. listofQObjects :: set_parents_list(QObject * parent) { for (int i = m_list_ofQobjects.count(); i>0; i--) { m_list_ofQobjects[i-1]->setParent(parent); } } I don't know if is it "right way", I even found here somebody uses my earlier version with additional list (but it's unsafe for sure). The best explanation how to manage memory in qt I found here. If there is better way to do so, please share.

@Chris-Kawa thank you .

Using setText will avoid useless delete/allocation of items.

When you set the item, The table takes ownership of the item. So just deleting the tableWidget should satisfy. If you want to selectively delete, what you are doing should be good enough.