Today I implemented two little features:
Example:
Imagine a part called 123456789.dat
When you take a look into the sourcecode with LDPartEditor, you will get a "~Moved to"-warning , because s\123456789s01.dat looks like this:
and refers to a red 4518.dat, which was ~Moved to 4518a.dat.
The integrated quick-fix feature can now transform
into
- Deep Inlining (with BFC conformity)
- "~Moved to" error correction: The texteditor displays now an error (in the list of errors, no pop-up!) when a "~Moved to" reference was used. Additionally, there is a possibility that the user can select and auto-fix this error, even if the "~Moved to"-file has a different origin or redirects to another "~Moved to".
However, if the reference is not direct (means that a normal subfile from your part uses a "~Moved to") you will still get a message that you should take a look into the subfile, because the subfile refers to a "~Moved to")
Example:
Imagine a part called 123456789.dat
Code:
0 Foo
0 Name: 123456789.dat
0 Author: Nils Schmidt [BlackBrick89]
0 !LDRAW_ORG Unofficial_Part
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
0 BFC CERTIFY CCW
1 16 0 0 0 1 0 0 0 1 0 0 0 1 s\123456789s01.dat
When you take a look into the sourcecode with LDPartEditor, you will get a "~Moved to"-warning , because s\123456789s01.dat looks like this:
Code:
0 Baz
0 Name: s\123456789s01.dat
0 Author: Nils Schmidt [BlackBrick89]
0 !LDRAW_ORG Unofficial_Subpart
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
0 BFC CERTIFY CCW
1 0x2FF0000 0 0 0 1 0 0 0 1 0 0 0 1 4518.dat
and refers to a red 4518.dat, which was ~Moved to 4518a.dat.
The integrated quick-fix feature can now transform
Code:
1 0x2FF0000 0 0 0 1 0 0 0 1 0 0 0 1 4518.dat
into
Code:
1 0x2FF0000 0 4 20 1 0 0 0 1 0 0 0 1 4518a.dat