Hello Dinko,

thank you very much for your review and response!

Yea true, this mostly happens if the RadTextBoxControl is not the only column (or specifically not the first column).

For reference, I replaced all the RadTextBoxes with RadTextBoxControl after I needed to use them at a few points. As it's a native TPF control, it has a themed and cusotmizeable context menu. The highlight color looks more modern and some few other details. Using both different TextBoxes lead to an inconsistent design (due size, context menu, visual difference) I wanted to avoid. Also I want to ensure I can fully access the features of a RadTextBoxControl when I need them without replacing it before. I see the RadTextBox is perfectly for migrating projects, but like to replace those with the most native RadTextBoxControl after some time and build new applications directly with it.

Also, I'm using full AutoSize on most flyouts and dialogs as a customizeable sizing is absolutely not requierd and mostly not inteted here. Only the main form or specific other forms are not AutoSize and fully cusotmizeable.

Looking fordward for possible fixes in the future. :)

Wish you a nice day!

Best regards,
Pascal

I know this fix will only work for the if RadTextBoxControl is part of a fully AutoSized Form. As soon as the Form is AutoSize=false it will not work anymore.

Tried to rewrite the patch, but honestly I miss one parameter for indication at this point. That means the issue is at Size calculation somewhere probably.

However, I hope this all infos help you to find the root issue.

Thank you very much. :)

[HarmonyPatch("ProcessAutoSizeChanged")]
[HarmonyPatch(typeof(RadTextBoxControl))]
internal class MyPatch
{
    public static void Postfix(bool value, object __instance)
    {
        if (__instance is not RadTextBoxControl @this)
            return;
        var found = false;
        var parent = @this.Parent;
        while (parent != null)
        {
            if (!parent.AutoSize)
            {
                found = true;
                break;
            }
            parent = parent.Parent;
        }
        @this.RootElement.StretchVertically = value && !found /*&& ???*/;
        @this.RootElement.SaveCurrentStretchModeAsDefault();
    }
}

I think I found the root cause of this. The method overwrite in "RadTextBoxControl" for "ProcessAutoSizeChanged()" sets  the "RootElement.StretchVertically" property to "false" whenever AutoSize is enabled.

Possible solution: When you comment out this line of code then the RadTextBoxControl autosizes normally.

I wrote a harmony patch to explicitely ignore this line. It works fine!

Not sure why this line is neccessery but I'm sure there is an intention behind. However, I need to ignore this line to be able to use RadTextBoxControl as full drop-in replacement in all my dialogs.

Possible (real) solution -> Add a static property like "RadTextBoxControl.AutoStretchOnAutoSize" that can be disabled on program start, if required. If disabled, the overwrite method "SaveCurrentStretchModeAsDefault()" would just do nothing.

Another example at runtime:


This came up after migrating all RadTextBox controls to RadTextBoxControl controls and enable AutoSize like it was on RadTextBox and how it is required for the layout to size completely automatically.