On Friday 06 November 2015 16:45:33 Knoll Lars wrote: > To me this points strongly to opt for never unloading plugins. We can of > course offer a way to force the unloading if the user does it's own stuff > and knows what he's doing. But Qt should probably never unload any plugins > it loads, as we do not control those and don't know whether they are safe > to unload. > > With that we're ok for the plugins we load. And if someone else insists on > unloading something it's his problem.
I'm leaning towards that too. But before I go and modify QFactoryLoader... what is that class for? Can anyone find out from the old history? It traces its existence back to "Long live Qt 4.5". -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
