First of all thanks both for your answers.
I must say my last message contains a bad word : “editing” … I meant “give acces to Edit menu” so the Person view but not to do changes.
I was then speaking about and only in a browsing situation to make deductions and so on to prepare for future research.
Yes @emyoulation there are alternatives and the one you give is very helpfull in some cirumstance.
But note that using gramplets add clicks too, tab navigation and don’t always avoid to get multiple windows.
Multiple windows isn’t a problem for me while browsing the database ( i undestand it’s kind different when changing data and so on).
I thought it was intuitive, easy and quicker to just use double-clik to browse the base.
@DaveSch
When you say “The problem exists in understanding what is being edited from within which view.”, you say all.
I must say the way Gramps reuse existing stuffs is very very clever as that avoid “tons” of dialog boxes, reduce the code size and simplify its managment.
The counterpart is it’s (very) difficult to translate that in an intuitive manner inside the interface.
As it is the case here : as you say, yes, it can be considered as logic to get the child relation when we do double-click in Family view but in People view
we expect more the person dialog of the child.
As People view reuses Family view when you double-click a marriage in People view we get the child relation dialog when we double-click a child and not the person dialog.
And as Family, Events, Places, Sources, Citations, Repositories, Media and Notes categories are intuitively interpreted as lists and no more, that doesn’t simplify the challenge to obtain an intuitive interface.
Best regards.