depends if they aren't shown there for a good reason or not.
ie how would be this vs showing all output inthe view with maybe the hidden ones as rtanslucent?

depends if they aren't shown there for a good reason or not.

I don't know. @romangg
Showing them is easy, they're just visible: model.enabled basically but I don't know what other implications changing that has.

In D24687#547976, @mart wrote:

depends if they aren't shown there for a good reason or not.
ie how would be this vs showing all output inthe view with maybe the hidden ones as rtanslucent?

Disabled outputs shouldn't be shown in their full representation (even if slightly transparent) in the overview since they are not part of the view/overall screen geometry as long as they are disabled.

I thought about showing some mini-symbols for disabled outputs on one of the sides of the overview at a fixed position. But for that a proxy model would make sense I guess. I have never used one but from my understanding with that we could then show a simple list view of all disabled outputs on the side.

@broulik: Is it simple to implement such a proxy model? I would like to avoid another combo box and make instead all enabled and disabled outputs being selectable from the overview in some way as described above. That being said if it's too big of a change for backporting or will take too much time till next bug fix release we can go with the combobox as an intermediate solution to improve the situation on 5.17.

I thought about showing some mini-symbols for disabled outputs on one of the sides of the overview at a fixed position.

What do you need a proxy model for that? The outputs are part of the model, just visible: model.enabled. You could just have the delegate look differently and be positioned somewhere else and non-draggable when it is disabled?

This is a big improvement IMO. You can also remove the little dots at the bottom too. +1 for getting it into 17.1.