Resizing autoscale graphs to allow for increased screen dpi

The screen on our desktop (which runs WD) has to be set at 150% dpi. This means that autoscale graphs are cut off around the edges when uploaded e.g. http://cavershamweather.org.uk/autoscaletemphum.gif .

Is there anything I can do to fix this?

yes
there is a setting to reduce the size of the auto scale graphs, by a %, in the auto scale graph window
see my weather page for how small you can get them

At first I put 67%, and then 20%, but the graphs are still cut off around the edges :frowning:

then you are doing some thing wrong, as it does work OK (it works for me)
can you post a screen shot of what you have done

Sure, http://aycu39.webshots.com/image/14038/2005005474546576067_rs.jpg

hard to see all the settings with the scroll bars in the way
so you have eh switch on in the custom setup?
is the web gif image smaller that before?
why do you have to have your desk top set like that?

Yes, custom switch is on, and no, graph hasn’t changed size at all.

The computer is used by my mum who has poor eyesight

Do you have any more ideas? Perhaps you could briefly try increasing your dpi to see what effect it has.

humm
zip and email me your settings files and I will test here, with that dpi setting, and your settings
see in the faq for how to send those settings

Hi Dan100

I have this problem. How did you resolve it? Or was it not resolved?

Cheers,

Rick

there is a thread on how to change the DPI settings in windows…in the FAQ I think
check that out

Found this in an old post and thought it might help…

Thanks Dan. I did that and both were already set to “Normal”. So, I guess Windows is not the problem, eh? :?

Cheers,

Rick

Can you post a screen grab that shows the exact problem you have?

G’day again Dan,

Actually, I have been trying to address this issue in two separate posts. You can get more detail on the issue at my post titled, “Problems with setting and maintaining font size in WD main screen”. The reason I came to here is because someone said that the problem could have been Windows DPI. I did a search on DPI and found this earlier post and resurrected it.

Please let me know if you need further information – that the other post is not clear enough.

Cheers,

Rick