The designer always uses fixed pixel coordinates, no scaling for resolution.
The client can scale. Each window and container and component has layout properties that control its scaling behavior, if any, and the impact on fonts. You should study that part of Inductive University.
One of the first rules for Vision: Design at the smallest size practical - ideally, lower than any actual client’s resolution. It’s much, much easier to Vision to scale up practically than to scale down.
It’s unfortunate that your design has the tab strip ‘anchored’ to the right size. There’s no good way to do that in Vision, because the tab strip just isn’t flexible in that way (it’s not a ‘real’ JTabbedPane, it’s a custom component pretending to be one). You could maybe switch to using something like a multi-state button; it’ll require more effort to look the same, but not that much.
Where is the padding around the outside coming from? I would do that with a thick border on the root container, rather than trying to position components “inside” the edges - that way, there’s no way for a component to sneak ‘past’ the edge, also.
Are your unit labels separate labels on the root container? You could try grouping/containering the value + label, or even making a template for the repeated unit + label set. Then you shouldn’t have to worry about overlap and scaling quite as much.
