The dialog is quite small right now, could it be increase by,
lets say 100 pixels?
Done.
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
Jerome,
That should be fixed now.
/cvsroot/ParaView3/ParaView3/Qt/Components/pqChangeInputDialog.cxx,v
-- Qt/Components/pqChangeInputDialog.cxx
new revision: 1.4; previous revision: 1.3
Utkarsh
On Fri, Mar 19, 2010 at 10:51 PM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
Oh isn't it
Now I miss an edit box or alike that shows your selection for every
input! I think this is important, at least I scrolled around to see what
the edit boxes say with the actual form in the first place! :)
Utkarsh Ayachit wrote:
Folks,
I've committed some changes. A slight change from the
Thanks Utkarsh
I like it ! However - let me know if I am boring ;) -, for multiple inputs
on
one port (such as AppendGeometry), it would be nice if the current inputs
are already selected when choosing Change Input in the pipeline
browser. Lazy men (yes, I am) don't want to reselect them...
Oh isn't it already? Looks like there's a bug with multiple input
connections. I'll fix it.
On Fri, Mar 19, 2010 at 4:36 AM, Jérôme jerome.ve...@gmail.com wrote:
Thanks Utkarsh
I like it ! However - let me know if I am boring ;) -, for multiple inputs
on
one port (such as AppendGeometry),
I vote yes for the mockup!
Utkarsh Ayachit wrote:
I agree, the pipeline preview is confusing and for the most part
useless. Unless people object, I'd vote for removing it as well.
Attached is a sample mockup. In case of filters like Append which have
single input port, but multiple input
My 2 cents on this :
It seems to me that the input list is provided in alphabetical order. In my
case I have a lot of custom plugins that take 2 inputs, one being
vtkImageData
and the other a vtkPolyData (such a stream tracer with custom source).
Depending on wich is the 'principal' input, the
you get my vote!
On 15 March 2010 23:58, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote:
I agree, the pipeline preview is confusing and for the most part
useless. Unless people object, I'd vote for removing it as well.
Attached is a sample mockup. In case of filters like Append which have
I am not sure why there's a problem. In your case, your filters have 2
input ports. e.g. in the stream tracer case, referring to the mockup,
INPUT1 will be called Input while INPUT2 will be called
ArbitrarySource or Source as the case may be. Both of which
allowing the user to only add 1 item in
Then I was right : I was not clear enough!
First, I talked about the current panel, not your mockup. I agree with
those who enthousiastic.
Second, the problem I noted on the multiple-input-port panel is that
the input are not ordered by index, but by name. Changing Source
to ArbirtraySource in
One simple fix would be to make sure that the preview window isn't
selectable. A lot of my users get confused thinking one box is for
the input and the other as the source.
Regards,
Paul
On 12 March 2010 19:10, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote:
I cannot agree more. I am going
See comments below,
Christian Werner wrote:
As a user, may I present three suggestions, two of which should be
very easy and still yield an improvement.
1) remove the Pipeline Preview: This may be rude because it's somehow
nice. But then again, you cannot change what happens to the pipeline
I agree, the pipeline preview is confusing and for the most part
useless. Unless people object, I'd vote for removing it as well.
Attached is a sample mockup. In case of filters like Append which have
single input port, but multiple input connections, the use can type in
a comma separated list of
Hello!
I wonder why the input port selection is so cramped in the input editor.
It is really bad that you cannot actually read out the selections you
make without moving the scrollbar. Then, after scrolling, you cannot
change the other input without scrolling back. This really steals your
I cannot agree more. I am going to take a stab and fixing this before
3.8. We've just had too many complaints about this dialog to keep on
delaying this.
Utkarsh
On Fri, Mar 12, 2010 at 2:00 PM, Christian Werner
christian.wer...@rwth-aachen.de wrote:
Hello!
I wonder why the input port
Now that it is brought up, we should put this dialog on the list of things to
redesign. There are a lot more problems with it than obscured widgets.
-Ken
On 3/12/10 12:10 PM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote:
I cannot agree more. I am going to take a stab and fixing this
Added to the list:
http://paraview.org/ParaView3/index.php/ParaView_Usability_Improvements#Miscellaneous
On Fri, Mar 12, 2010 at 2:54 PM, Moreland, Kenneth kmo...@sandia.gov wrote:
Now that it is brought up, we should put this dialog on the list of things
to redesign. There are a lot more
17 matches
Mail list logo
