Change Details

Since enabling global area writing (ef4aa42ea4ff), loading a file in old Blender versions would cause `wmWindow.global_areas` to be read, since there was already reading code for it and `ScrAreaMap` was in SDNA. However the `ScrArea.global` of the global areas would be `NULL`, because it was *not* in SDNA (`ScrGlobalAreaData` was excluded). The code however assumes that areas in the global area-map have a valid `ScrArea.global` pointer. Think this was a mistake in 5f6c45498c92. We should have cleared all this data on reading, until the global area writing was enabled.

Since enabling global area writing (ef4aa42ea4ff), loading a file in old Blender versions would cause `wmWindow.global_areas` to be read, since there was already reading code for it and `ScrAreaMap` was in SDNA. However the `ScrArea.global` of the global areas would be `NULL`, because it was *not* in SDNA (`ScrGlobalAreaData` was excluded). The code however assumes that areas in the global area-map have a valid `ScrArea.global` pointer. Think this was a mistake in rB5f6c45498c92. We should have cleared all this data on reading, until the global area writing was enabled.

Since enabling global area writing (ef4aa42ea4ff), loading a file in old Blender versions would cause `wmWindow.global_areas` to be read, since there was already reading code for it and `ScrAreaMap` was in SDNA. However the `ScrArea.global` of the global areas would be `NULL`, because it was *not* in SDNA (`ScrGlobalAreaData` was excluded). The code however assumes that areas in the global area-map have a valid `ScrArea.global` pointer. Think this was a mistake in rB5f6c45498c92. We should have cleared all this data on reading, until the global area writing was enabled.