-
Notifications
You must be signed in to change notification settings - Fork 62
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
Entity-specific gizmo configuration in bevy integration #56
Comments
To clarify with an example: if an entity has |
The current system does not support entity-specific configuration, but something like that |
Yeah sounds good. Does the current underlying gizmo implementation support turning off certain axes e.g. for entities which should only be translated in the x and z axes (then the gizmo would only show the relevant arrows)? This would be another feature that would be nice to have in the entity-specific gizmo config if it was implemented! |
The current main version does not yet support that, but that is implemented in the |
Is there any way with the current system to configure certain
GizmoTarget
s to not be editable in certain gizmo modes? For example, I want some entities to not be rotatable and some not scaleable (the gizmo would just do nothing to those entities' rotations/scales if edited in that mode).I'm not exactly sure of the best way this could be implemented (unless it is already possible and I'm missing it!). Perhaps an optional
GizmoTargetConfig
component which contains properties such asuse_rotation
/use_scale
. If the entity has bothGizmoTarget
andGizmoTargetConfig
, the config options would be applied to that specific entity. This approach could be good, as it would open the door to potentially more entity-specific gizmo config options in the future.The text was updated successfully, but these errors were encountered: