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
Fastrope animations and in-line privatization #5501
Conversation
|
||
#define ANIMS_HOOK ["extendHookRight", "extendHookLeft"] | ||
#define ANIMS_DOOR ["door_R", "door_L", "CargoRamp_Open", "Door_rear_source", "Door_6_source", "CargoDoorR", "CargoDoorL"] | ||
#define ANIMS ["dvere1_posunZ", "dvere2_posunZ", "doors"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we find a different name for this macro? "Anims" is so generic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are they for? The names aren't really descriptive. Could use ANIMS_BENCH
, ANIMS_RAMP
, or ANIMS_RAIL
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ANIMS_DOOR
-> animateDoor
(requires "door" source)
ANIMS
-> animate
("user" source)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only reason they are split in two is because they require different commands (above comment).
I have no idea what else to name it, suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ANIMS_USER
then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I named them ANIMS_ANIMATEDOOR
and ANIMS_ANIMATE
to make clear what command is which. Is that good or should I go with ANIMS_DOOR
and ANIMS_USER
rather? One is what command is used, the other is what type is used in config.
When merged this pull request will:
onPrepare(/Cut)Common
functions