How do I change the indent from the "Arrow" to the Icon in the Connection tree?

Hello,
I think this issue could be related to the high dpi. Could you verify the scaling you currently have so we could reproduce it exactly?

In the meantime you can try to tweak this setting:



Regards

The zoom setting is exactly the same as yours, I attach a screenshot of my settings from this section.

And what if I downgrade the version to 2022.3.24.0 (with the settings saved), all the indents between the arrows will fall into place, and everything will be beautiful as always!!! And I'll raise the version, everything will move out again... clearly the problem is in the RDM code

That's how it looks beautiful on the 24th release, on all releases further, the distance between the arrows moves down (((

We will investigate, it might need to rescale the value prior to sending it the UI control.

That was it, I scaled my Windows to 175% before the fix I had

now with the proper scaling code I have


This will be in the next release. (v2022.3 and v2023.1)

Best regards,

Will you release a fix in the RDM code in the next release ?

so that with talo it is as beautiful as it was throughout all releases up to 2022.3.24.0

PS:
And by the way, when you increase by 175, you still don't have the same as it was on the 24th release, count by pixels. Compare my screenshot above with the 24th version and yours that turned out, you have significantly less indentation between the arrows

This was caused by changes were made about two months ago to solve this issue for a user.
https://forum.devolutions.net/topics/38501/too-long-indent-now

It's obvious now that we didn't test enough scenarios. This led to this and other discussions and eventually we found the issue.

The issue we have now is that since we've added High DPI scaling on the value (example @ 175%, 14 becomes 24). We need to reset all users overrides since someone who manually changed it to 24 already will see the value become 42 @ 175% a this is bad.

So the question I have for both are:

• What DPI scaling are you at?
• What value looks on your machine?
• We currently use 14 as a default value. Is this still good? Should it be 16? 12? Other?

Best regards,

For 6 years now I have been using only a 4k monitor

1. Resolution 3840 x 2160
2. Windows scaling can be used as 150% (default) and 175 % (before version 2022.3.24.0 , everything was fine with both options !! after your new changes, everything became terrible, all the arrows moved out)
3. In RDM, I always had the setting: Height of the structural type element = 18
4. Tree view item height = 14 (and in 6 years of using RDM on a 4k monitor, I have never changed these values)
5. 14 for me it was always great at any scaling (you definitely don't need to change it) on a 4k monitor, after the release of 2022.3.24.0 everything became terrible (((

Return everything as it was, 4k monitors are coming into use more and more, and even ordinary laptops now have a resolution of 2k and 4k, and before the parameters that you had on 18/14, they were ideal for shooters!!

PS
More or less beautifully and locanically, the tree with arrows now looks only at a value of 28 (Tree view item height = 28) , but at the same time everything is moving out in other places...

Thank you for the information.

4. Tree view item height = 14 (and in 6 years of using RDM on a 4k monitor, I have never changed these values)

This is a new option, so prior versions you didn't have it and we didn't set any value override in the control. Since it's a "non-exposed" value of our third-party control, we had to test/tweak the "best fit value". We went with 14 but that doesn't look to be good for everyone.

Here is what I suggest we do.

Change the option to be optional. (see image). The default will be unchecked and will make RDM behave as before. For those users where they need to first check the box and set the value according to their needs.



Sorry for making it somewhat complicated but we have to work with the constraints that third party UI control gives us.

Best regards,

In version 2022.3.35.0 there is no such check box to cancel this element (screenshot attached)

Hello,

The engineering team has not yet implanted the fix, we will notify you once it is available.

Best regards,