From 9afd7a22af73e3ba8517dae1859ce4a65d4a3f1c Mon Sep 17 00:00:00 2001 From: TurtleHero Date: Fri, 18 Oct 2019 09:54:58 -0700 Subject: [PATCH] Fix 'explicitely' -> 'explicitly` --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f49324f5c..ce3b3fc8c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -216,5 +216,5 @@ Keep the element on the stack if possible. If you need a pointer or have complex #### QObject classes - Use the [object tree](https://doc.qt.io/qt-5/objecttrees.html#) to manage lifetime where possible. Objects are destroyed when their parent object is destroyed. -- If you have to explicitely delete an object use `variable->deleteLater()` instead of `delete variable`. This ensures that it will be deleted on the correct thread. +- If you have to explicitly delete an object use `variable->deleteLater()` instead of `delete variable`. This ensures that it will be deleted on the correct thread. - If an object doesn't have a parent consider using `std::unique_ptr` with `DeleteLater` from "src/common/Common.hpp". This will call `deleteLater()` on the pointer once it goes out of scope or the object is destroyed.