zcy
/
dust3d
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
dust3d/src/bonemark.h

91 lines
4.8 KiB
C
Raw Normal View History

Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
#ifndef DUST3D_BONE_MARK_H
#define DUST3D_BONE_MARK_H
#include <QColor>
#include <QString>
enum class BoneMark
{
None = 0,
Neck,
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
Limb,
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
Tail,
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
Joint,
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
Count
};
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
#define BoneMarkHasSide(mark) ((mark) == BoneMark::Limb)
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
QColor BoneMarkToColor(BoneMark mark);
#define IMPL_BoneMarkToColor \
QColor BoneMarkToColor(BoneMark mark) \
{ \
switch (mark) { \
case BoneMark::Neck: \
Fix rig Improve the quality of main body resolving.
2018-11-07 08:02:55 +00:00
return QColor(0xfd, 0x64, 0x61); \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
case BoneMark::Limb: \
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
return QColor(0x29, 0xfd, 0x2f); \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
case BoneMark::Tail: \
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
return QColor(0xff, 0xfd, 0x38); \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
case BoneMark::Joint: \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
return QColor(0xcf, 0x83, 0xe1); \
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
case BoneMark::None: \
return Qt::transparent; \
default: \
return Qt::transparent; \
} \
}
const char *BoneMarkToString(BoneMark mark);
#define IMPL_BoneMarkToString \
const char *BoneMarkToString(BoneMark mark) \
{ \
switch (mark) { \
case BoneMark::Neck: \
return "Neck"; \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
case BoneMark::Limb: \
return "Limb"; \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
case BoneMark::Tail: \
return "Tail"; \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
case BoneMark::Joint: \
return "Joint"; \
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
case BoneMark::None: \
return "None"; \
default: \
return "None"; \
} \
}
BoneMark BoneMarkFromString(const char *markString);
#define IMPL_BoneMarkFromString \
BoneMark BoneMarkFromString(const char *markString) \
{ \
QString mark = markString; \
if (mark == "Neck") \
return BoneMark::Neck; \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
if (mark == "Limb") \
return BoneMark::Limb; \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
if (mark == "Tail") \
return BoneMark::Tail; \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
if (mark == "Joint") \
return BoneMark::Joint; \
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
return BoneMark::None; \
}
QString BoneMarkToDispName(BoneMark mark);
#define IMPL_BoneMarkToDispName \
QString BoneMarkToDispName(BoneMark mark) \
{ \
switch (mark) { \
case BoneMark::Neck: \
return QObject::tr("Neck"); \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
case BoneMark::Limb: \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
return QObject::tr("Limb"); \
case BoneMark::Tail: \
return QObject::tr("Tail"); \
Add new rig type: Generic The difference between tetrapod and generic is that, with tetrapod, all the bones need to be generated are know before mark, so if some marks are missing, there would be a message prompted; with generic, you can mark what ever marks as you wish, and the algorithm is try to create a spine and the limbs growing on the spine, that means, the generated skeleton would be some kind of creature.
2018-11-01 15:24:06 +00:00
case BoneMark::Joint: \
Unify rig type of generic and tetrapod as animal Marks also reduced to four types: Neck, Limb, Tail and Joint.
2018-11-06 16:26:19 +00:00
return QObject::tr("Joint"); \
Cleanup Many source file name and data type are prefixed by "skeleton" before, now all are refactored. The class MeshResultContext represents the outcome of mesh generation before, now we have material, pose and animation, so we just rename it as Outcome.
2018-10-25 00:19:38 +00:00
case BoneMark::None: \
return QObject::tr("None"); \
default: \
return ""; \
} \
}
#endif