 |
This is something I cannot provide for the moment being. The source text is parsed and interpreted, but comments contained in the declaration body are inevitable lost by this process - they are not ignored by the parsing code, it doesn't even see them. To change that behaviour the parsing approach would need to change completely to produce syntax trees including trivia, like the roslyn framework is doing. For now, any change to the material will lose whitespace and comments. |
 |
That's a shame - so I suppose for any change no matter how small, the material has to be reconstructed from the parsing and interpretation output. So my suggestion of only updating the image paths themselves would be no good. Unless it's possible for the Material Editor just to take the current material source text, Find&Replace the paths, then feed it back into the parser? |
|
|
Any text manipulation is rather dangerous and might do more harm than good. If the search string is occurring more than once then this is most likely not doing what it should. |
|
|
I've split of parts of the report into another issue 0006052, because losing keywords is not something that should happen and could be caused by some different problem. |
- Anonymous
