Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Numbering in FilterEvents #7372

Closed
AndreiSavici opened this issue Feb 2, 2013 · 1 comment
Closed

Numbering in FilterEvents #7372

AndreiSavici opened this issue Feb 2, 2013 · 1 comment
Assignees
@wdzhou
Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done.
Milestone
Release 3.1

Comments

@AndreiSavici
Copy link
Member

In FilterEvents the workspaces are numbered from 0. If you choose to group these, an algorithm will act on the group, but the output workspaces are numbered from 1. Change FilterEvents to output good data from 1.

With the new option, first the unfiltered workspace will be not output. Then the other workspaces will start from index 1 and be consecutive. No workspace will be removed even if there is no event inside.
@AndreiSavici
Copy link
Member Author

This issue was originally trac ticket 6526

@AndreiSavici AndreiSavici added Low Priority Things that you don't ever want to be done. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@AndreiSavici AndreiSavici added this to the Release 3.1 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wdzhou wdzhou

Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done.
Projects
None yet
Milestone
Release 3.1
Development

No branches or pull requests
2 participants
@AndreiSavici @wdzhou