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

Rather than hidePastFuture or showMomentOnly, use mapFilter #38

Closed

GoogleCodeExporter opened this issue Mar 28, 2016 · 1 comment

Labels

auto-migrated Priority-Low Type-Task

GoogleCodeExporter commented Mar 28, 2016

just a tweak I don't have time for right now - the API for specifying map 
filters should take a string or a function, rather than specifying specific 
filters as attributes.

Original issue reported on code.google.com by nick.rab...@gmail.com on 18 Feb 2009 at 7:10

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Type-Task auto-migrated Priority-Low labels

GoogleCodeExporter closed this as completed

Author

GoogleCodeExporter commented Mar 28, 2016

Fixed in trunk - TimeMap objects now take a mapFilter parameter, which can be 
set to
a string (e.g. 'showMomentOnly') or an actual function.

Original comment by nick.rab...@gmail.com on 15 Jul 2009 at 1:21

Changed title: Rather than hidePastFuture or showMomentOnly, use mapFilter
Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment