Re: [Interest] Syncing tree views.

2016-07-30 Thread Ch'Gans
On 30 July 2016 at 03:51, william.croc...@analog.com wrote: > >>> >>> IIRC: The first 'L' in LGPL stands for 'Lesser', not 'Library'. >> >> >> For version 2 (which the above text refers to), it was called >> "Library". You are free to use the later versions, whatever name they now >> have. >> See

Re: [Interest] Syncing tree views.

2016-07-29 Thread william.croc...@analog.com
IIRC: The first 'L' in LGPL stands for 'Lesser', not 'Library'. For version 2 (which the above text refers to), it was called "Library". You are free to use the later versions, whatever name they now have. See https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html Very good. - I do n

Re: [Interest] Syncing tree views.

2016-07-29 Thread Christoph Feck
On Friday 29 July 2016 17:14:08 william.croc...@analog.com wrote: > On 07/29/2016 11:07 AM, Christoph Feck wrote: > > On Friday 29 July 2016 16:58:31 william.croc...@analog.com wrote: > >> On 07/29/2016 10:33 AM, Christoph Feck wrote: > >>> On Friday 29 July 2016 16:14:41 william.croc...@analog.com

Re: [Interest] Syncing tree views.

2016-07-29 Thread william.croc...@analog.com
On 07/29/2016 11:07 AM, Christoph Feck wrote: On Friday 29 July 2016 16:58:31 william.croc...@analog.com wrote: On 07/29/2016 10:33 AM, Christoph Feck wrote: On Friday 29 July 2016 16:14:41 william.croc...@analog.com wrote: applies to items which are common to both.) KF5 has a solution for t

Re: [Interest] Syncing tree views.

2016-07-29 Thread Christoph Feck
On Friday 29 July 2016 16:58:31 william.croc...@analog.com wrote: > On 07/29/2016 10:33 AM, Christoph Feck wrote: > > On Friday 29 July 2016 16:14:41 william.croc...@analog.com wrote: > applies to items which are common to both.) > >>> > >>> KF5 has a solution for that. I'm not an Model/View

Re: [Interest] Syncing tree views.

2016-07-29 Thread william.croc...@analog.com
On 07/29/2016 10:33 AM, Christoph Feck wrote: On Friday 29 July 2016 16:14:41 william.croc...@analog.com wrote: applies to items which are common to both.) KF5 has a solution for that. I'm not an Model/View expert, but i think this is what you're looking for: https://api.kde.org/frameworks/ki

Re: [Interest] Syncing tree views.

2016-07-29 Thread Christoph Feck
On Friday 29 July 2016 16:14:41 william.croc...@analog.com wrote: > >> applies to items which are common to both.) > > > > KF5 has a solution for that. I'm not an Model/View expert, but i > > think this is what you're looking for: > > > > https://api.kde.org/frameworks/kitemmodels/html/classKLink

Re: [Interest] Syncing tree views.

2016-07-29 Thread william.croc...@analog.com
applies to items which are common to both.) KF5 has a solution for that. I'm not an Model/View expert, but i think this is what you're looking for: https://api.kde.org/frameworks/kitemmodels/html/classKLinkItemSelectionModel.html Thanks for the pointer. Alas... - I am industry and this is

Re: [Interest] Syncing tree views.

2016-07-29 Thread Ch'Gans
On 29 July 2016 at 22:25, william.croc...@analog.com wrote: > Hello: > > This is a desk top widgets question. > No QML here. > > I have two QTreeView instances. > They both use the same base model, > but differ in subsequent layers of proxy models. > > What is the most convenient way to keep then

[Interest] Syncing tree views.

2016-07-29 Thread william.croc...@analog.com
Hello: This is a desk top widgets question. No QML here. I have two QTreeView instances. They both use the same base model, but differ in subsequent layers of proxy models. What is the most convenient way to keep then in sync. When an index is selected in one, I want the corresponding index to