Just solved. Using the suggested tool we could send our ideas to some other partners and one answer did the trick.

##The solution##

The only way to solve this issue with enough usability for Winforms apps and keeping code simplicity (at least for the first version) and all was to:

1. Create something similar to checkboxes where the user can select from none to all filters available to the report (each report has it's very own list of available filters based on the report's data).
2. After the filters are selected, the user moves to the next page and there he sees only the selected filters (or a message like "You haven't selected any filter") to configure items, ranges and all.
3. After that the filters are applied to the data and the wizard moves to a page with a running marquee-bar.

Motivation

We needed something that could be simple to code and yet, usable for most users.

Users of our systems do share some similarities and with this approach we're taking that into account too.

It's important to notice that this is the first version of this new feature. It's yeat a beta version and we will be collecting feedback from this (and other) features.

This is a very new feature and it's most like to change over time. I was planning to deliver some major improvements here but the feature itself is already a major improvement and the interface will be refactored over time.

Once again: we want to keep code simple. Since the feature is already very complex, it's important to keep everything else simple for now.

Just solved. Using the suggested tool we could send our ideas to some other partners and one answer did the trick.

The solution

The only way to solve this issue with enough usability for Winforms apps and keeping code simplicity (at least for the first version) and all was to:

1. Create something similar to checkboxes where the user can select from none to all filters available to the report (each report has it's very own list of available filters based on the report's data).
2. After the filters are selected, the user moves to the next page and there he sees only the selected filters (or a message like "You haven't selected any filter") to configure items, ranges and all.
3. After that the filters are applied to the data and the wizard moves to a page with a running marquee-bar.

Motivation

We needed something that could be simple to code and yet, usable for most users.

Users of our systems do share some similarities and with this approach we're taking that into account too.

It's important to notice that this is the first version of this new feature. It's yeat a beta version and we will be collecting feedback from this (and other) features.

This is a very new feature and it's most like to change over time. I was planning to deliver some major improvements here but the feature itself is already a major improvement and the interface will be refactored over time.

Once again: we want to keep code simple. Since the feature is already very complex, it's important to keep everything else simple for now.

Just solved. Using the suggested tool we could send our ideas to some other partners and one answer did the trick.

Thanks!

Just solved. Using the suggested tool we could send our ideas to some other partners and one answer did the trick.

##The solution##

The only way to solve this issue with enough usability for Winforms apps and keeping code simplicity (at least for the first version) and all was to:

1. Create something similar to checkboxes where the user can select from none to all filters available to the report (each report has it's very own list of available filters based on the report's data).
2. After the filters are selected, the user moves to the next page and there he sees only the selected filters (or a message like "You haven't selected any filter") to configure items, ranges and all.
3. After that the filters are applied to the data and the wizard moves to a page with a running marquee-bar.

Motivation

We needed something that could be simple to code and yet, usable for most users.

Users of our systems do share some similarities and with this approach we're taking that into account too.

It's important to notice that this is the first version of this new feature. It's yeat a beta version and we will be collecting feedback from this (and other) features.

This is a very new feature and it's most like to change over time. I was planning to deliver some major improvements here but the feature itself is already a major improvement and the interface will be refactored over time.

Once again: we want to keep code simple. Since the feature is already very complex, it's important to keep everything else simple for now.