「利用者:Walid shouman/GoogleSummerOfCode/2013/GettingStarted」の版間の差分
(Created page with "Here I'm stating all the issues/development faced before the official starting date -------------------------------- = Scene set up = //TODO: -----------------------------...") |
細 (1版 をインポートしました) |
(相違点なし)
|
2018年6月29日 (金) 05:56時点における最新版
Here I'm stating all the issues/development faced before the official starting date
目次
Scene set up
//TODO:
6th of June
worked on
- Making the CustomData_bmesh_copy_data work for the BMesh blocks to transfer color loops in progress 70%
achieved
- Understood the arguments of the function and where to find them mainly (more details will be found below)
- Written the first Not working ^_^ BMesh transfer ... which I claim that it will work for the Mesh datatypes (more details below)
- Tracked the mesh_vertex_color_add function that adds a new Vertex Color group to the mesh (which clarified many things actually)
The full story
- Answering point 1) and 3) in Achieved
I decided to track the operation of adding a new vertex color layer to figure out how those data are being stored as CustomData CD_MLOOPCOL and where to find them exactly. (noting that I knew in advance that they are being stored as Custom Data of that type)
The following picture should illustrate the tracking process (enough talking ^_^)
- Answering point 2) in Achieved
at the point of the first hint its declared Mesh* me ... I tried and used BMesh* bm and figured out that the ldata information disappeared ... which I relied one them while calling the function [CustomData_bmesh_copy_data(&bm_src->ldata, &bm_dst->ldata, &bm_src->ldata.layers[index].data, &tmp2);] that's considered the core of transferring any BMesh Custom Data
My proposed solution for now is to try executing the function now with Mesh* me_src, me_dst; instead of BMesh* bm_src, bm_dst; till I know the reason :)
template:
th of June
worked on
achieved