Re: [Paraview] source with optional input port

2010-01-27 Thread Utkarsh Ayachit
Burlen, Sorry for the delay in responding. I guess your solution is fine. Ideally, I'd have liked tuples of group-names and proxy-names, but that'd break backwards compatibility and really isn't such a common use-case :), so not worth the to trouble. Feel free to commit your patch -- just makes s

Re: [Paraview] source with optional input port

2010-01-04 Thread burlen
Happy New Year Utkarsh, What is the user wants the panel for (readers, MyReader) and (filters, MyFilter) but not (readers, MyFilter)? To be honest I hadn't anticipated the situation but, as far as I can tell this scenario is OK under the proposed change because the group is tested first and if

Re: [Paraview] source with optional input port

2009-12-21 Thread Utkarsh Ayachit
That sounds reasonable, but specification of multiple group names and xml names and the m*n matching between them seems funny. Any ideas on how we can make that more explicit? What is the user wants the panel for (readers, MyReader) and (filters, MyFilter) but not (readers, MyFilter)? Not sure if i

[Paraview] source with optional input port

2009-12-18 Thread burlen
Hi folks, I'd like to have a PV data source that can be used either as a source(without an input dataset) or as a filter(with an input dataset). Based on what I have observed, to accomplish it the source has to show up both in the sources menu and the filters menu, which is easy to do with th