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.

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

Dynamic Boundary Calculations #8

Open
Xevion opened this issue May 24, 2020 · 2 comments
Open

Dynamic Boundary Calculations #8

Xevion opened this issue May 24, 2020 · 2 comments
Labels
state: approved Approved to proceed. type: experimental May introduce difficult problems or require innovative implementations to be successful. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used.

Comments

@Xevion
Copy link
Owner

Xevion commented May 24, 2020

The Boid code should be revised to allow for dynamic specification of 'Boundaries'.
Boundaries are spaces where Boids should avoid or inversely, drawn into. Additionally, the code should support more than one boundary - with different options like the forces that are applied to Boids, the range, the bias, the type (draw in/out) and anything else needed.

This could create some very amusing and fun behaviour:

  • Boundaries around UI elements pushing Boids
  • Custom boundaries for the user
@Xevion Xevion added type: feature Brand new functionality, features, pages, workflows, endpoints, etc. state: approved Approved to proceed. work: complicated The situation is complicated, good practices used. type: experimental May introduce difficult problems or require innovative implementations to be successful. labels May 24, 2020
@Xevion
Copy link
Owner Author

Xevion commented May 24, 2020

I forgot to mention, but this behavior could work with LeanTween if the calculations are not difficult to implement. For example, when an tween is in progress, a callback updating the boundary based on the current position of the text would be a good idea, but this may be difficult to implement if LeanTween does not allow users to slip in a callback.

If LeanTween does not allow this functionality, the only other way would be checks implemented on Update(), but this may drag down performance long term if I'm not careful.

@Xevion
Copy link
Owner Author

Xevion commented May 24, 2020

Another Boundary related feature would be spherical boundaries - these would be pretty easy to implement, seeing how a simple distance/radius check would suffice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: approved Approved to proceed. type: experimental May introduce difficult problems or require innovative implementations to be successful. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: complicated The situation is complicated, good practices used.
Projects
Road to Release
  
Awaiting triage
Development

No branches or pull requests

1 participant