You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially, it's possible for NULL FormIDs to get passed to various RecordProcessors if they exist in some of the sub-records. Sometimes, it's OK for there to be a NULL FormID there, sometimes it's not, but the current workings of the class don't allow for checking of the information, or even reporting which record had the NULL FormID in one of its sub-records.
The first bit can be solved with smarter passing of FormIDs to op.Accept, the second will require refactoring so RecordProcessor can have the information needed to display a better warning message.
As it is currently, most cases can be safely ignored, and it just leads to confusion.
The text was updated successfully, but these errors were encountered:
Brought up originally here: wrye-bash/wrye-bash#101
Essentially, it's possible for NULL FormIDs to get passed to various RecordProcessors if they exist in some of the sub-records. Sometimes, it's OK for there to be a NULL FormID there, sometimes it's not, but the current workings of the class don't allow for checking of the information, or even reporting which record had the NULL FormID in one of its sub-records.
The first bit can be solved with smarter passing of FormIDs to
op.Accept
, the second will require refactoring so RecordProcessor can have the information needed to display a better warning message.As it is currently, most cases can be safely ignored, and it just leads to confusion.
The text was updated successfully, but these errors were encountered: