Re: [Interest] Persistence of editor for openPersistentEditor

2018-06-05 Thread Patrick Stinson
That is logically consistent, though it didn’t work for me. findChildren() still returns two objects. strange. > On Jun 5, 2018, at 3:42 AM, william.croc...@analog.com wrote: > > On 06/04/2018 05:08 PM, Patrick Stinson wrote: >> Hello! >> >> I am writing a unit test for an item view and need to

Re: [Interest] Persistence of editor for openPersistentEditor

2018-06-05 Thread Reinhardt Behm
On Tuesday 05 June 2018 06:42:28 william.croc...@analog.com wrote: > On 06/04/2018 05:08 PM, Patrick Stinson wrote: > > Hello! > > > > I am writing a unit test for an item view and need to get . The code in > > *qabstractitemview_p.h* “releases” an editor created by a delegate by > > calling *QObj

Re: [Interest] Persistence of editor for openPersistentEditor

2018-06-05 Thread william.croc...@analog.com
On 06/04/2018 05:08 PM, Patrick Stinson wrote: Hello! I am writing a unit test for an item view and need to get . The code in *qabstractitemview_p.h* “releases” an editor created by a delegate by calling *QObject::deleteLater()* on it. However, in the following code the first editor is not delet

[Interest] Persistence of editor for openPersistentEditor

2018-06-04 Thread Patrick Stinson
Hello! I am writing a unit test for an item view and need to get . The code in qabstractitemview_p.h “releases” an editor created by a delegate by calling QObject::deleteLater() on it. However, in the following code the first editor is not deleted and so the second call to findChild still retur