Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
As I understand it, the Rotoscoping effect is somewhat new. It would appear that the bug comes as a side effect from how keyframes for the effect are serialized into a JSON document: QJsonDocument has a fromVariant function which takes a QVariantMap to construct an object.
QVariantMap is effectively a map which uses QStrings as keys, so KeyframeModel::getRotoProperty string-ifies the raw frame index of each keyframe for the key. Problem is, the width parameter for the rightJustified is miscalculated.
1-digit frame indices get 0-padded to 2 digits with a leading 0, but 3-digit frame indices and up are unchanged. As the ordering in QVariantMap is based on the ordering of the keys, the keyframes end up serialized into JSON, and written into the project XML, out-of-order.
You end up with a JSON array where the JSON object representing keyframe (let's say) 102 immediately follows keyframe 0, then keyframe 10, 11 ... 19, 200, 201 ... then 20, 21, and so on.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
