# Order of Pipeline Browser Objects

**URL:** <https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685>\
**Category:** ParaView Support\
**Created:** [December 22, 2021, 10:05pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685 "2021-12-22T22:05:50Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)\
**Post date:** [January 4, 2022, 3:24pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685/21 "2022-01-04T15:24:45Z")

</div>

Of course, sources have no inputs.

I understand your need now. Not supported, although would be nice.

---

<div class="post-metadata">

**Author:** ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)\
**Post date:** [January 4, 2022, 3:25pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685/22 "2022-01-04T15:25:46Z")

</div>

You may be interested by the node editor plugin though:

> [@Official Node Editor in ParaView ?](https://discourse.paraview.org/t/official-node-editor-in-paraview/6295/9):
>
> Since it looks like this conversation is the most up-to-date on the discourse regarding the node editor, I’ll just point some informations here : the node editor has been officially merged into ParaView, see : [https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/4952](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4952) there’s issues already logged in the repo at [https://gitlab.kitware.com/paraview/paraview/-/issues/20726](https://gitlab.kitware.com/paraview/paraview/-/issues/20726) so everyone is aware of what the current limitations are. Feel free to add/resolve/comment stuff on this issue if …

---

<div class="post-metadata">

**Author:** ![natetron](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/n/d78d45/32.png) [@natetron](https://discourse.paraview.org/u/natetron)\
**Post date:** [January 4, 2022, 3:29pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685/23 "2022-01-04T15:29:57Z")

</div>

Is there an official way for suggestions/requests like this to be logged for future versions of PV? Thank you for your help and consideration.

---

<div class="post-metadata">

**Author:** ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)\
**Post date:** [January 4, 2022, 3:30pm UTC](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685/24 "2022-01-04T15:30:47Z")

</div>

> **[Feature Requests](https://discourse.paraview.org/c/feature-requests/14)**
>
> Request features for future versions of ParaView. If a feature you want to see in ParaView has already been added to this category, please vote for it by liking the first post in the topic.

Actually @Venke understood this faster than me. You should just like venke proposal.

You should also consider contacting Kitware for a faster inclusion of this feature:

> [@How are features and bug fixes incorporated into ParaView?](https://discourse.paraview.org/t/how-are-features-and-bug-fixes-incorporated-into-paraview/4735):
>
> As with all open source projects, adding features and fixing bugs takes developer effort. That effort may originate from volunteer community contributors, or through paid professional services offered by companies like [Kitware](https://www.kitware.com). Features and bug fixes are prioritized by the needs of contributing community members and by professional services customers. Note that contributions are vetted by a rigorous community review and testing process; therefore it is recommended that significant changes are d…

[Previous page](https://discourse.paraview.org/t/order-of-pipeline-browser-objects/8685.md?page=1)
