-
|
Oh boy, it's one of those days.... I've got a couple of structs in my project that will... cascadingly create a bunch of .conflict files whenever something "conceptually near them" is updated? But I can't figure out why. Even after recreatring every struct linked to this, even after recreating the structs themselves that seem like they might be the problem.. editing some struct will make a bunch of .conflict duplicates that have 0 changes, again and again and again. But why?????? Has anyone encountered anything like this before? What should I be looking for? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
@ghidra1 this looks like the same behavior I mentioned in #8381 As for dealing with this, I've found that replacing existing conflicts seems to help, especially if a .conflict type is associated with a data type archive when it shouldn't be made a conflict to begin with. |
Beta Was this translation helpful? Give feedback.
@ghidra1 this looks like the same behavior I mentioned in #8381
As for dealing with this, I've found that replacing existing conflicts seems to help, especially if a .conflict type is associated with a data type archive when it shouldn't be made a conflict to begin with.