Skip to content

Add additional interface to put on Environments for controlling if a Callback may be used #1010

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
Closed
Vexatos opened this issue Apr 3, 2015 · 1 comment
Closed

Add additional interface to put on Environments for controlling if a Callback may be used #1010

Vexatos opened this issue Apr 3, 2015 · 1 comment
Milestone
v1.5.7

Comments

@Vexatos
Copy link
Contributor

Vexatos commented Apr 3, 2015

Just a reminder for @fnuecke. Maybe some interface that has a shouldAddCallback(world, x, y, z, callbackname) or something like that, you probably already have a better idea. Just make sure it also works for ManagedEnvironments added by Drivers.
@fnuecke fnuecke added this to the v1.5.7 milestone Apr 11, 2015
@fnuecke
Copy link
Member

fnuecke commented Apr 11, 2015

Added an interface implemented by Environments, FilteredEnvironment. Provides a single method, boolean isCallbackAvailable(String name), takes only the name of the callback to test for, since all other info should be available in the env itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.5.7
Development

No branches or pull requests
2 participants
@fnuecke @Vexatos