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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2110.0. "V3.0 Read-Wide Option?" by ODIXIE::MCLELLAN (Make it so, Mr. Data!) Mon Jan 18 1993 21:49

    In V2.4 we had a customisation which allowed documents to be Read in
    wide (132 column) mode. This is the same as doing a normal Read
    followed by a GOLD-E (too tricky for some users!)
    
    The script set symbol $READ_WIDE to "Y" before doing a 'MAIL READ'.
    This 'hack' does not work under V3.0. I also tried a pre-function on
    OA$LIST which called OA$LIST_WIDTH_WIDE, but it still came out as
    80-column mode - (Probably the pre-function is executed before the
    scoundrel that assumes I want 80 column mode).
    
    Is there any way I can set up a Read-Wide option for the customer which
    will work for V3.0 ?? (Thought of updating the PROFIL field READ$WIDE
    but this seems a little drastic - inefficient and likelihood of it
    remaining in wrong state).
    
    Colin McLellan
    Monsanto Site Resident (Pensacola)
T.RTitleUserPersonal
Name		DateLines
2110.1$READ_WIDE is now the profile field READ$WIDESCOTTC::MARSHALLSpitfire Drivers Do It ToplessTue Jan 19 1993 02:2310
    In V3.0 the PST symbol $READ_WIDE has been replaced by the profile
    field READ$WIDE.  See the script OA$LIB:PST_TO_PROF.SCP (written by a
    truly wonderful engineer :-) which is run as part of the (post-)
    installation to populate this and other new (in V3.) profile fields
    from the corresponding PST symbols.
    
    You'll need to WRITE CHANGE PROFIL this field instead of changing the
    PST symbol to get the functionality you require in V3.0
    
    Scott
2110.2US SWCIOSG::MAURICEBecause of the architect the building fell downTue Jan 19 1993 11:156
    Also users themselves can change the setting on the second form of the
    Set Working Conditions form.
    
    Cheers
    
    Stuart
2110.3Changing profil.read$write no worse, maybe betterIOSG::SHOVEDave Shove -- REO2-G/M6Tue Jan 19 1993 15:1512
    Actually, changing the profile field READ$WIDE will be no more
    expensive than what you were doing, i.e. changing the PST symbol
    $READ_WIDE (which will involve a write to the user's PST file). In
    fact, as the PROFILE file is buffered, it may even be cheaper. (Also,
    if the user's subprocess has been created, changing $READ_WRITE would
    involve a write to the subprocess as well).
    
    And as for it staying in the wrong state, this is exactly as it was -
    your change would get saved in the user's PST just as the new change to
    READ$WRITE will get saved in the Profile.
    
    Dave.
2110.4Thanks, with minor modificationODIXIE::MCLELLANMake it so, Mr. Data!Tue Jan 19 1993 21:0214
    Thanks for the help. To clarify the original problem, the 'Read-Wide'
    needs to be done on a *temporary* basis, so having the user change his
    PROFIL from SWC is not appropriate.
    
    Using the method in .3 (write change profil), I found that I needed to
    add:
    
    	oa$ini_globals
    
    to make it work. (I think this sets the symbol OA$PROFIL_READ_WIDE
    which is probably what the code looks for).
    
    Thanks again,
    Colin McLellan