[Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter

[Utkarsh Ayachit]

Totally agreed. The pipeline browser hasn't been updated since early
ParaView 3.0 days, I'd guess a 2009. It surely can be made better. In the
end, it boils down to the need and time availability. Since it works well
for 80/90% of the cases, we (and our customers and contributors) often end
up prioritizing other features and bug fixes. We do offer various
consulting options <https://www.kitware.com/what-we-offer/#consulting>, if
you're keen on getting it updated 😊.

Utkarsh

On Fri, Mar 31, 2017 at 6:00 PM, Jonathan Borduas <
jonathan.borduas at caboma.com> wrote:

> Hi Utkarsh,
>
> Thank you for your answer. As a user, especially with a complex tree, I
> found this unpractical. I have the reflex when searching for a filter to
> scroll down if the filters is "afterward".
>
> I do prefer the GitTree representation of ParaViewWeb. My opinion is that
> a GitTree could be the optimal representation of the pipeline.
>
> The GitKraken GitTree could be a good inspiration for a redesigned
> pipeline browser 😊.
>
> Best regards
>
> Jonathan Borduas
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Friday, March 31, 2017 2:25 PM
> To: Jonathan Borduas <jonathan.borduas at caboma.com>
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Pipeline not respecting the arrow of time after
> changing the inputs of a filter
>
> Jonathan,
>
> The arrow is not intended to have a "top/down" direction, just a
> "back-to-root" direction. It can be interpreted as "ProgrammableFilter1"
> can be found somewhere on the main trunk.
>
> On Thu, Mar 30, 2017 at 11:21 PM, Jonathan Borduas <
> jonathan.borduas at caboma.com> wrote:
> >
> > Dear ParaViewers,
> >
> >
> > I came across some weird behaviour in ParaView: We have a custom
> > BooleanOperation filter that have two outputs (custom ParaView build).
> > If both outputs are the inputs of an Append Geometry and we update the
> > inputs of the BooleanOperation Filter, the Append Geometry will be
> > moved before the BooleanOperation Filter.
> >
> >
> > I always though that if there was any dependencies in a pipeline, the
> > representation would respect the "arrow of time" that goes from top to
> > bottom.
> > Please look at the picture here attached (same behaviour with a
> > ProgrammableFilter instead of a Append Geometry).
> >
> >
> > Is my comprehension at fault here or is it a bug ?
> >
> >
> > Thank you,
> >
> >
> > Jonathan Borduas
> >
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170331/b7af4def/attachment.html>