# Scale fontsize as percentage of screenheight?

**URL:** <https://forums.fusetools.com/t/scale-fontsize-as-percentage-of-screenheight/3622>\
**Category:** How-to Discussions\
**Created:** [February 28, 2016, 9:58am UTC](https://forums.fusetools.com/t/scale-fontsize-as-percentage-of-screenheight/3622 "2016-02-28T09:58:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin1](https://avatars.discourse-cdn.com/v4/letter/m/3be4f8/32.png) [@martin1](https://forums.fusetools.com/u/martin1)\
**Post date:** [February 28, 2016, 9:58am UTC](https://forums.fusetools.com/t/scale-fontsize-as-percentage-of-screenheight/3622/1 "2016-02-28T09:58:14Z")

</div>

Hi,

Coming from WPF a technique often used there is to scale text relative to the screen height.

I’m trying to translate this to fusetools, but I’m stuck.

I’d like to do something like this

\< Grid Rows=“10\_,90\_”\> \< Decorator ux:Name=“FontSizeRef” Row=“0”/\> \</ Grid \>

\< Text FontSize="{FontSizeRef.ActualHeight}\>Test\</ Text\>

Is there a way to do this is in Fuse, or what approach do you recommend?

(The ux code in this post is really not formatting as I expected)

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [February 28, 2016, 12:07pm UTC](https://forums.fusetools.com/t/scale-fontsize-as-percentage-of-screenheight/3622/2 "2016-02-28T12:07:54Z")

</div>

Hi,

This sort of binding will create a feedback loop and is therefore not possible in Fuse.

A way to acheive this today is to use `Viewbox`, it will scale its content to fill the available space:

```auto
<Grid Rows="10,90">
    <Viewbox>
        <Text FontSize="100">Test</Text>
    </Viewbox>
</Grid>

```

`FontSize` must simply be large “enough”, so i picked 100 here, assuming that’s larger than the maximum actual size you will display.

I’ve made ticket to investigate “better” ways to do this in the future. Thanks for posting!