Page MenuHome

Editor Transform Refactoring
Open, Confirmed, MediumPublic

"Love" token, awarded by brilliant_ape."Love" token, awarded by jc4d."Love" token, awarded by Mets."Love" token, awarded by bnzs."Love" token, awarded by amonpaike."Like" token, awarded by capnm."Yellow Medal" token, awarded by duarteframos.
Assigned To
Authored By



As stated by anyone who has worked on the transformation code, the current code situation is a mess.
It tries a generic solution using callbacks for each type of transformation: rotation, scaling, translating, to sphere, shear, shrink/fatten, bone size, edge/vert slide and others.

The initial idea is good, but with the constant addition of new features, some files have now more than 9000 lines of code, and it is not uncommon to find old workarounds.


Other solutions can be added later as the refacor is in process.

Once one of the changes listed is done on a branch or patch it can be applied to the master. (It's a huge and dynamic project, so it doesn't seem practical to split attention on different branches).


To Do

Event Timeline

Germano Cavalcante (mano-wii) lowered the priority of this task from Needs Triage by Developer to Confirmed, Medium.Aug 19 2019, 8:09 PM