u-he

Sendy · Post by **Sendy** » Fri May 11, 2012 2:54 am

Text is hard to read when GUI isn't normal size.

What do I win?

(I was going to report this bug but forgot...)

Breeze · Post by **Breeze** » Fri May 11, 2012 3:14 am

LOL

Urs is already aware... there's just been too many other things to take care of, which I get (and appreciate!!). But I use the large GUIs all the time and use the notes area quite a bit, so it's just really annoying... and common to the entire line of u-he products.

I.hopthey...gtarnd...toi...soon...

stuman · Post by **stuman** » Fri May 11, 2012 3:27 pm

I hope they get around to it soon

Urs · Post by **Urs** » Fri May 11, 2012 3:43 pm

stuman wrote:I hope they get around to it soon

Me too.

Breeze · Post by **Breeze** » Fri May 11, 2012 4:09 pm

Urs wrote:Me too.

Maybe the trick is to implement a clever and highly sophisticated abbreviation algorithm that allows for intelligibility despite abbreviation.

Urs · Post by **Urs** » Fri May 11, 2012 6:56 pm

The actual problem is that the code that measures the length of a text in pixels is not aware of the gui resize factor. I don't know why it does that, but if I ever suss it out then things won't need abbreviation anymore

Breeze · Post by **Breeze** » Sun May 13, 2012 9:52 pm

Urs wrote:The actual problem is that the code that measures the length of a text in pixels is not aware of the gui resize factor. I don't know why it does that, but if I ever suss it out then things won't need abbreviation anymore

Couldn't that just be solved by a fractional multiply factor applied according to the GUI size selected and rounded off to the nearest pixel?

u-he

KVR Audio

Tex..s...hrd.torea..whn...UIisn..norml...siz...