CogitoDoor Improvements

[BryceBarbara]

Here's some ideas for improvements to the CogitoDoor node.

1. Make it a @tool script and use _validate_property to hide properties that aren't relevant in the current context. For example, is_sliding being true means open_rotation_deg, closed_rotation_deg, bidirectional_swing, and use_z_axis can be hidden.
2. Instead of use_z_axis, use the pattern set in cogito_turnwheel.gd where you define a rotation axis. This would allow doors to rotate on any axis or even multiple axes.
3. Switch the open_rotation_deg and closed_rotation_deg properties to radians and use the @export_range flag with the radians_as_degrees hint. This will avoid calls to deg_to_rad.
4. Add a is_disabled property that disables movement and has no interaction_text. This will allow for things like doors that are only controlled programmatically or doors that initially don't indicate they're doors (think hidden doors).

[Phazorknight]

Hey, thanks for these suggestions.

The Cogito Door was one of the first things I made, so there's quite a few areas it can be improved.
Making the inspector only display the relevant properties depending on the "mode" would be great, the rotation code could be improved quite a bit overall as well (I'm thinking more towards just setting two rotation vector3's and tweening/lerping between them.

Will look into it and play around a bit.

The 4th point is already doable: simply don't add the Cogito Door to the 2nd collision layer and it won't get picked up by the player interaction. There's examples of those in the Legacy demo scene (the drawbridge) and the Lobby demo scene (hidden door).

[Phazorknight]

@BryceBarbara I've just pushed an update that cleans up the Door inspector a bit using the property validation.
Haven't done any more improvements to the rotational properties yet.

[BryceBarbara]

You did great and the code is much more readable. Trying to figure out which animation mode a certain line of code was operating under was quite the mental exercise.