Closed Wuzzy2 closed 8 years ago
I see this pattern twice:
float myFriction = 0.0;
if(!theProps.property2Float(Property::FRICTION_STRING, &myFriction))
theProps.setDefaultPropertiesString(Property::FRICTION_STRING + QString(":/"));
Please use this member of the PropertyList
class instead:
bool doesPropertyExists(const QString &aKey) const;
It keeps our code cleaner and performs less operations.
Ehm. No. Please take another look at your logic. I think you're introducing an interesting bug.
I noticed the list of available properties in the editor are pretty chaotic: Key properties were missing from many objects, while other objects had properties available which don't make sense for that object.
This PR aims to fix this by making sure the available properties make more or less sense. The properties were chosen by technical feasability, i.e. they have to work in the first place, not whether if it always make sense to use them.
But please check for yourself together with the objects test level
test-objects.xml
.