Christoph, The issues Alan pointed out are indeed some of the concerns. It's been that and priorities of the sources that fund ParaView development that we never got around to investigating this too deeply or coming up with an all encompassing solution. Maybe we start by picking a small set of readers to start adding this support to and that could be a good way to attack this.
If we were to come with with such as readers list, what would those be? Utkarsh On Tue, Jan 14, 2014 at 4:09 PM, Christoph Grüninger < [email protected]> wrote: > Hi Scott, > thanks for your clarification. I wasn't aware of the fact, that > the reload button has to be written for every reader. > Now I see that it will be a lot of work to get the reload button. > On the other hand, reader by reader this feature could be implemented. > > I am using the VTK reader and will try Sebastien's work around. Thanks > so far. This won't cover the numerious wishes for the reload button > but alleviate my pain. > > I am still wondering why Kitware / the ParaView devs do not communicate > the reasons better. I know users switching to VisIt only due to its > reload button. Please update your statements on uservoice and the bug > tracker. Otherwise people might think you don't listen. > > Thanks for the answers, > Christoph > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview >
_______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
