Strange change of column name when inserting special unicode chars
I have a VST in reprot mode and some columns defined in the header. Now I want to implement some kind of word wrap and had the idea to insert Unicode char U200D at that place of the word where VST is allowed to wrap. U200D is a zero width space so I had hoped it could detect that and wrap there.
I'm not so much after not wrapping there, but as soon as I insert this char and select a different property of the column in Object Inspector the name of the column in the colums list tool window changes to COlumn10 (it is column 10), even if the text is still the German text I gave the column.
When I remove this special unicode char and select a different property the name in the list is the German name I have given. => as soon as that special char is in that name the list "misbehaves", because the column at runtime still displays my entered German name.
Of course one could think of allowing special chars (like such a zero width space char - there are similar ones around that code point which might even be better suited) to indicate where the wrap may occur, because as is it looks like you have to have space chars in your text for the wrapping occur. But with this technique you could define several points in long words and VST could pick the best one and when the user changes column width better adjust to it...
The text is drawn using the Windows API function DrawText() which also does word wrap when using the flag DT_WORDBREAK. Not sure if it supports U200D or something similar.
I'm not so much after not wrapping there, but as soon as I insert this char and select a different property of the column in Object Inspector the name of the column in the colums list tool window changes to COlumn10
Is this behavior specific for Virtual TreeView or does it happen with other string properties in Delphi as well?
Most likely related to #1154 and no activity since 4 months, therefore closing this issue.
I do think that's the same case as 1154. Sorry for creatign a duplicate! The behavior is design time wise and not run time wise.