<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/modscaleform/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/modscaleform/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 25 Feb 2008 21:48:32 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/modscaleform/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Form truncated when current screen res &lt; design resolution</title><link>https://sourceforge.net/p/modscaleform/bugs/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have several forms (with subforms) that were developed for 1280 X 1024 x 96 (and which use most of the screen) that I tried displaying on a wide-screen format laptop monitor (1280 x 800).  The lower portion of the screens (i.e. that which would normally display on lines 801 thru 1024) are truncated / not displayed.  I think the problem is that Access is automatically truncating the form within the opening window size so from that point forward the scaling logic continues to scale the truncated shape.&lt;/p&gt;
&lt;p&gt;I suspect that there needs to be some logic that determines how big the window WOULD have been (based on the header / detail / footer heights) compared to what was actually allocated in order to determine if Access has truncated the form initially.  It should then be possible to calculate compensating ratios to use during the scaling.  If attached an example of what one of the forms should look like (unscaled) verses how it is actually displaying.  I'm happy to provide a working sample if that would assist.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BAM</dc:creator><pubDate>Mon, 25 Feb 2008 21:48:32 -0000</pubDate><guid>https://sourceforge.net4b480217a5b9dccf68cd84ff3048cb9b19f1c8da</guid></item></channel></rss>