Fix dirty handling

Author: franzpoeschel

src/RecordComponent.cpp

@@ -251,11 +251,13 @@ RecordComponent &RecordComponent::resetDataset(Dataset d)
         }
         else if (d.dtype != Datatype::UNDEFINED)
         {
+            setDirty(true);
             return makeEmpty(std::move(d));
         }
         else
         {
             rc.m_dataset = std::move(d);
+            setDirty(true);
             return *this;
         }
     }

src/backend/BaseRecord.cpp

@@ -776,11 +776,16 @@ inline void BaseRecord<T_elem>::flush(
     }
 
     if (!this->written() && this->empty() && !this->datasetDefined())
+    {
         // Verify upon ScientificDefaults::finalize() that the Record has been
         // populated. For now, we will assume that data will come later; ignore
         // this Record at the moment.
+        //
+        // If any of the properties above will change, the Record will become
+        // dirty through it.
+        this->setDirty(false);
         return;
-
+    }
     /*
      * Defensive programming. Normally, this error should yield as soon as
      * possible.

src/backend/BaseRecordComponent.cpp

@@ -46,6 +46,7 @@ BaseRecordComponent &BaseRecordComponent::resetDatatype(Datatype d)
     {
         rc.m_dataset = Dataset{d, {1}};
     }
+    setDirty(true);
     return *this;
 }