View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004114ParaView(No Category)public2006-12-01 10:182007-02-05 15:15
ReporterKen Moreland 
Assigned ToMark Richardson 
PriorityurgentSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0004114: Multiple filter inputs
DescriptionThe pipeline browser needs to support filters that have multiple inputs (fan-in).
TagsNo tags attached.
Project
Topic Name
Type
Attached Files

 Relationships

  Notes
(0006047)
Mark Richardson (reporter)
2006-12-22 14:41

The change input dialog allows the user to add sources to multi-input filters. I tested it with the append filter.
(0006079)
Ken Moreland (manager)
2007-01-03 17:42

Two requested changes:

1. If you select multiple objects in the pipeline browser and then create a multi-input filter (like append), then all those objects should be added to the filter's input. This is how ParaView 2 behaves (and it makes a lot more sense than just picking one).

2. In the Input Editor dialog box, would it be difficult to change the interaction so that a click simply toggles the selection for multi-input filters? The list of filters does not really look much like a list view widget (nor does it behave a lot like one), so if you had not initially told me I could select multiple things, I may never have thought to use shift/ctrl-click combinations.
(0006108)
Mark Richardson (reporter)
2007-01-08 18:06

In response to #2, I don't think it's a good idea to modify the selection behavior in the tree view for multiple input properties. The tree view is a lot like the pipeline browser's tree view, which does multi-selection in the same way (shift/ctrl+click). This type of selection behavior is also common. I'd like to stick with it to avoid the extra learning curve. Maybe we can add a label explaining how to use the dialog (like a wizard) or add some "what's this?" comments.
(0006109)
Ken Moreland (manager)
2007-01-08 18:55

I see your point. But I still don't agree.

Although the two views may be implemented with the same widget, the "feel" for the two is, I think, different enough to make a different interaction mode natural.

I'm not keen on the "explanation" label either. It implies that we know it's a confusing GUI but we decided to make the user figure it out rather than make something that made more sense.

You believe a different interaction mode is an "extra learning curve," whereas I contend the opposite is true. Let's agree to disagree and bring this up with the group in our weekly meeting to widen the opinion base.
(0006127)
Mark Richardson (reporter)
2007-01-09 12:45

You're right there wouldn't be an extra learning curve. I thought you were suggesting we invent a new selection behavior. I haven't used the toggle multi-selection before.

Even with the extra learning curve out of the equation, I still think we should be consistent. The change input dialog not only uses the same widget, it displays the same model. The only differences are the root of the model and the allowed actions (can't edit or select the filter subtree).

If we can agree that the gui should be consistent, then the question becomes, which type of selection should both the view use: extended (the current) or multi. I think the extended selection is more powerful. Do we make it platform dependent? Is multi selection a mac thing?
(0006128)
Ken Moreland (manager)
2007-01-09 13:35

After discussing with the group, we decided that we would keep the shift/ctrl+click interaction mode. However, in the list that you select from, that list will stay static rather than change every time you click. A new pipeline window will also be added to preview what the result of the operation will look like. This should be applied to both the single-input and multiple-input filters.

We can also add a label at the bottom of the dialog to remind users of shift-clicks and ctrl-clicks.
(0006151)
Mark Richardson (reporter)
2007-01-11 12:56

I added a separate preview pipeline to the dialog to show how the pipeline will look after the changes. The filter is selected in the preview so the user can keep track of where it moved. I also switched the order of the dialog to better follow the work flow.
(0006279)
Mark Richardson (reporter)
2007-01-29 17:11

The user can now select multiple sources as inputs when creating a multi-input filter. This works with the filter menu and the pipeline menu's add filter action.

 Issue History
Date Modified Username Field Change
2011-06-16 13:10 Zack Galbreath Category => (No Category)


Copyright © 2000 - 2018 MantisBT Team