Andreas Kling b29ff7b821 LibGUI: Don't use Core::Object::add() to instantiate dialogs ... Now that add() returns a WidgetType&, we can't rely on the parent of a GUI::Dialog to still keep it alive after exec() returns. This happens because exec() will call remove_from_parent() on itself before returning. And so we go back to the old idiom for creating a GUI::Dialog centered above a specific window. Just call GUI::Dialog::construct(), passing the "parent" window as the last parameter.		2020-03-04 21:04:06 +01:00
..
DirectoryView.cpp	Userspace: Use Core::Object::add() when building interfaces	2020-02-23 11:10:52 +01:00
DirectoryView.h	AK: Make Vector use size_t for its size and capacity	2020-02-25 14:52:35 +01:00
FileUtils.cpp	AK: Make Vector use size_t for its size and capacity	2020-02-25 14:52:35 +01:00
FileUtils.h	FileManager: Include sys/stat.h for struct stat	2020-02-05 18:39:45 +01:00
main.cpp	LibGUI: Don't use Core::Object::add() to instantiate dialogs	2020-03-04 21:04:06 +01:00
Makefile	LibGfx: Rename from LibDraw :^)	2020-02-06 12:04:00 +01:00
PropertiesDialog.cpp	LibGUI: Don't use Core::Object::add() to instantiate dialogs	2020-03-04 21:04:06 +01:00
PropertiesDialog.h	LibGUI: Don't use Core::Object::add() to instantiate dialogs	2020-03-04 21:04:06 +01:00