This content has been marked as final. Show 12 replies
Prabodh wrote:Tried it. No luck. Still I have to scroll down to see the bottom of the form. Only outer MDI window change according to formsweb height and width. The canvases/windows inside this has has no effect on this formsweb changes it seems.
Try specifying the height and width in formsweb.cfg as percentage rather than pixels. E.g. height=100% and width=100%
i have the same problem my winodow in the explorer brower rest in the same wieth and height ... i think that we have to change the configuration of the applet.. we have to change the height and wieth of the applet not the canvas ... my probem i foget where is this the location of the file in oracle directory....
Unlike many GUI applications, Oracle Forms does not "Auto-Scale" to fit the client display settings. If you design your application to 1024x768, then this is the minimum resolution required to display your application correctly. As one of your customers has discovered, when you run your Forms application in a lower resolution setting, then you must scroll left and right and up and down to see all of the items.
As Francois indicated, there are third party enhancements to try and compensate for this deficency in Oracle Forms but there is no "Oracle" provided solution to this issue.
You may want to notify your customer of your application's minimum resolution requirements.
Hope this helps,
If someone's response is helpful or correct, please mark it accordingly.
vbaprog wrote:Hi, where have we got to set this??? Formsweb.cfg??? I can't see a para with this name in that file.
Maybe you take a look at the "clientdpi"-parameter ...
Specifying w and h in the URL itself also does not have any effect.
François's 3rd party tool is unfortunately too expensive for us. :D
Edited by: user12240205 on Jul 17, 2012 10:08 PM
Edited by: user12240205 on Jul 17, 2012 10:12 PM
Specifies the dots per inch (DPI) and overrides the DPI setting returned by the JVM, allowing you to manage varying DPI settings per platform.
For example, a form developed on the Win32 platform may not display properly on the UNIX platform due to varying DPI values.
The clientDPI value can be any positive integer. Oracle recommends that you use an integer between 50 and 200.
Please take a look at:
10g => http://docs.oracle.com/cd/B14099_19/web.1012/b14032/configure003.htm#i1078752
11g => http://docs.oracle.com/cd/E16764_01/web.1111/e10240/appc.htm#BGBEHHGA
Add the HTM file (for example webutiljpi.htm) for parameter clientDPI:
<PARAM NAME="clientDPI" VALUE="%clientDPI%">
in the formsweb.cfg config section also add the parameter:
and then calling url:
by calling url:
And finally a modest request: Please read the documentation !
We had a problem where Web Forms users running on Macintosh platforms were having trouble viewing our forms, which are designed primarily to run on Windows platforms. Through experimentation, I found that running the Mac with this parameter in the URL enabled the users to see the text ok: &clientdpi=94
Windows users did not need a clientdpi parameter.
You can view this image to see the differences. Note the "Cred Emphasis" and "Cred Objective" lines. On the Mac, with the default ClientDPI (96), the prompt (boilerplate) text overlaps the data field. With ClientDPI set to 94, it was ok.
On the Windows platform, ClientDPI = 94 caused all the text to be smaller, and more difficult to read. The ClientDPI = 96 is the default. Setting ClientDPI to 104 caused the text to collide, similar to the Macs' default setting.
Also note that changing ClientDPI did NOT change the distance between fields on the screen. The ONLY thing it affects is the font size.