[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference clusta::acms

Title:ACMS comments and questions
Notice:This is not an official software support channel. Kits 5.*
Moderator:CLUSTA::HALLAN
Created:Mon Feb 17 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4179
Total number of notes:15091

4099.0. "acms/tdms font size problem" by CSC32::J_HENSON (Don't get even, get ahead!) Fri Feb 07 1997 16:05

acms 4.0 ->4.1, vax, ovms v6.1, tdms 1.9a, decforms ?.? -> v2.1b

I just spoke with a customer who recently upgraded (see above).  Since
the upgrade, they have been experiencing some unusual behavior in their
screen output.  FYI, the customer is LEGO.

Most of the tasks use tdms requests.  Those that don't use dcl
servers that run a rally script.  Currently, their only use
of decforms is to drive the menu.

Some of their tdms requests change the screen width from 80 to
132.  When it does this, the font size is also smaller, as expected.
When they exit the request, they change the screen width back to
80.  When they do this and either go to another task or back to
the menu, the font size stays as if it is still in 132 wide mode.

This also occurs if they change the screen width to 132 in a
dcl server, execute their rally stuff, and change it back to
80 before exiting the server.

Does any of this sound familiar to you?  They are running standalone.
However, I do not now if they have the logical set to force tdms
processing in the CP.  I can find out if necessary.

I have suggested that they see what happens if they define forms$manager
to be NL: and take decforms completely out of the picture.  I'll
post those results when (if) I get them.

Any other ideas?

Thanks,

Jerry
T.RTitleUserPersonal
Name		DateLines
4099.1CSC32::C_BENNETTThu Feb 13 1997 15:1852
    In the form realm I have seen this before.   The typical
    cause is a situation where a form product displays a 
    132 column form and DOES NOT REMOVE the 132 column form
    before attempting to DISPLAY A 80 COLUMN FORM.    
    
    DECforms has a REMOVE post display clause and/or a 
    REMOVE response step which should be used to take the
    132 column panel off from  the display before the 80
    column form is displayed.   
    
    (if you want to see a test case of this - let me know)
    I am still working at getting up to par ACMSwise so that 
    I can duplicate issues like this to see/feel this for ourselves. 
    
    As for TDMS,  RDU (request definition utility) has a 
    CLEAR SCREEN statement which executes before displaying 
    the TDMS form.    TDMS forms are the complete screen...
    
    (not to overlook the obvious)...
    
    In FDU be sure the screen width for the form specifices
    desired  setting - ie 
    
                              Form Attributes
    
               Attributes for Form Named: XXX
    
    Screen Background: [AS IS = 1; Black = 2; White = 3]    1
    
    >>>>Screen Width: [80 Columns = 1; 132 Columns = 2]         1
    
    Do you wish to assign default field attributes [Y/N]?   N
    
    HELP Form CDD Path-name: (Leave Blank If No HELP Form)
    
    
    
    
    
    
    Do you want Input Field Highlighting (If so, mark X below as required)
    [Y/N]? N
                Bold         Underscore         Blink         Reverse