Re: Simplifying KConfigDialogManager

2013-06-03 Thread David Faure
On Thursday 16 May 2013 08:13:55 David Edmundson wrote: > KConfigDialogManager currently contains a map of every possible widget > along with the name of the signal to connect to to know when a widget > changes. > > Can we kill this entire map and replace it with monitoring > widget->metaObject()-

Re: Simplifying KConfigDialogManager

2013-05-20 Thread Kevin Ottens
On Thursday 16 May 2013 08:13:55 David Edmundson wrote: > KConfigDialogManager currently contains a map of every possible widget > along with the name of the signal to connect to to know when a widget > changes. > > Can we kill this entire map and replace it with monitoring > widget->metaObject()-

Re: Simplifying KConfigDialogManager

2013-05-20 Thread Albert Astals Cid
El Dijous, 16 de maig de 2013, a les 08:13:55, David Edmundson va escriure: > KConfigDialogManager currently contains a map of every possible widget > along with the name of the signal to connect to to know when a widget > changes. > > Can we kill this entire map and replace it with monitoring > w

Simplifying KConfigDialogManager

2013-05-20 Thread David Edmundson
KConfigDialogManager currently contains a map of every possible widget along with the name of the signal to connect to to know when a widget changes. Can we kill this entire map and replace it with monitoring widget->metaObject()->userProperty()->notifySignal() at runtime? It will greatly simplify