Thanks for the info, someday i'll get around to digging into hlsl enough to actually understand...I was inspecting some VSL scripts when I recognized that one wasn't compiled. It didn't because of a compiler error of type "cannot convert from 'enumXYZ' to 'enumABC'". What happened? Name clash! The F&E manager ini file imported F&E definitions from other projects (thus not used in this project). One of my older projects and this one are using the same keyword for one of the their Enums: "none". 'None' is really a often used keyword, just like "left", "right", "on", "enable" etc.
I don't know where else this .ini would be really useful, when the editor would provide buttons for exporting and importing definitions via separate .ini/.xml files. Maybe just add a resource category with it, so if a developer needs to share or reuse enums or flags, just let him import them via drag and drop.
This .ini file made more trouble in the past then benefits, especially as the definitions are saved into the CMO anyways. This is probably one of the side effects from the lack of a proper project-management functionality for DEV. In meanwhile, you maybe want to delete that ini file often and/or prefix your enum-names with the type name.
