0

hide and seek

Well, not seek really.

 

I have always thought the way that Ninox hides the parent, when accessing the child through the parent is really neat. So e.g., click on a child line to open that child in the popup and the child's form is displayed without its parent being shown, even when it is displayed when viewing the child table directly. Makes sense as no need to show the parent when that is the actual main table.

However, the reverse is not the same.

From the child as the main table, click on a parent, the popup opens and the parent form also displays the list of children. I can understand why this might be appropriate when there are other children, but it makes no sense to display the child from which you started in the first place. Not only is that information redundant, but it allows you to click on the child and open that popup. From where you can again click on the parent and then the child and so on, ad infinitum as far as I can see. Allowing such an infinite loop is bad practice, but I cannot see how currently to prevent it.

 

Seems to me that when opening the parent, that form should not display that same child. If there are other children, then they can be shown, but if there is only the one child, then that children list should really not be displayed at all - in the same way the parent is hidden what accessing from a child.

 

In the case I'm currently struggling with, there will be only 1 child, so I really don't want to display it again when viewing the parent from the child, especially when the parent is 'embedded', as that constantly displays the same child record as currently being viewed. Simply hiding the field is no good really as then it is not available when accessing the parent directly.

 

Suggestions?

Reply

null

Content aside

  • 2 yrs agoLast active
  • 137Views