Fix save/export device issue on server-side

Author: serhmarch

README.md

@@ -3,6 +3,7 @@
 ## Overview
 
 Modbus Tools is set of program (client and server) with graphical user interface to work with standard Modbus Protocol. Modbus Tools are a free, open-source  tools with a simple user interface written in C++/Qt. It implements TCP, RTU and ASCII versions of Modbus Protocol.
+
 Software implements such Modbus functions as:
 * 1  (0x01) – `READ_COILS`;
 * 2  (0x02) – `READ_DISCRETE_INPUTS`;
@@ -17,13 +18,16 @@ Software implements such Modbus functions as:
 ## About Modbus Client
 
 The client implements access to a remote Modbus device. However, the client can work not only with one device, but with several devices that can be connected to a single network, which is especially useful when working with RTU and ASCII protocols, when access to all Modbus servers is realized through a single serial port. However, it can also be useful when using the TCP version of the protocol, for example, if you use the TCP->RTU bridge.
+
 All work is done within a single project. The main entities in the project are Port, Device and DataViewItem. Port contains network settings for both TCP/IP and serial ports. Device contains settings for a single device (such as Modbus Unit Address, etc.).  The DataViewItem contains a single data unit to be read from the remote device and has many formats to represent the current data.
 ![ModbusClient-img001](https://github.com/serhmarch/ModbusTools/assets/10882627/93fccbad-3eca-415f-8454-c0e8cd890d51)
 
 ## About Modbus Server
 
 The server implements Modbus server device and works like Modbus simulator. However, the server can  not only simulate single device, but can simulate several devices that can be connected to a single network, which is especially useful when working with RTU and ASCII protocols, when access to all Modbus servers is realized through a single serial port. However, it can also be useful to simulate Modbus network using the TCP version of the protocol, for example, if you use the TCP->RTU bridge, Modbus server can replace this bridge with remote devices for testing purposes.
+
 All work is performing within a single project. The main entities in the project are Port, Device, DataViewItem and Action. Port contains network settings for both TCP/IP and serial ports. Device contains settings for a single device (such as Modbus Unit Address, memory size etc).  The DataViewItem contains a single data unit to be read/write from the device and has many formats to represent the current data. Action provides simulation capabilities (automatic change of device memory values).
+
 ![ModbusServer-img001](https://github.com/serhmarch/ModbusTools/assets/10882627/e53d9d87-1b77-4f8c-9ad9-1b4c967219c7)
 
 ## Binary

bin/Ubuntu/x64/libcore.so

@@ -16,3 +16,7 @@ typedef QAtomicInt RefCount_t;
 ...
     mb::RefCount_t m_refCount;                 
 ```
+
+# 0.1.2
+
+Fix server-side bug when saving/exporting device