TfcTreeNode.WriteData/ReadData writes and reads Text, StringData1 and StringData2 properties as Ansi-strings.
This behaviour results into a problem in unicode applications, when the above mentioned strings contain characters that ar not in the current codepage, e.g. hebrew characters on Windows-1252: When the window/dialog is (re)created at runtime, which results in calling somewhere WriteData and ReadData, characters not in the current codepage will be replaced with the question mark.
I suggest to add a new boolean property like SaveAsUnicode to TfcTreeView, and to use one of the TfcNodeInfo.DummyPad bytes/bits as a flag to signal that the text properties are saved as unicode strings.
Please sign in to leave a comment.