[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

950.0. "/CAPTIVE limited to one menu?" by UTRTSC::BOSMAN (We're just sugar mice in the rain) Mon Jun 29 1992 08:57

    Hi,
    
    /CAPTIVE should limit where ALL-IN-1 searches for menu options.
    However, consider the next two scenarios:
    
    1 ALL-IN-1 V2.4) From MAIN:
                     <FORM FD /CAPTIVE
                     WP                  ! Not possible.
                     C
                     WP                  ! It's possible (?).
    2 ALL-IN-1 V3.0) From MAIN:
                     <FORM EMC /CAPTIVE
                     WP                  ! Not possible.
                     TR
                     WP                  ! It's possible (?).
    
    Question: Why is the second WP actually invoking the WP menu? Where has
    ALL-IN-1 found the WP option?
    
    Regards,
    Sjaak.
T.RTitleUserPersonal
Name		DateLines
950.1The name of the form?IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeMon Jun 29 1992 09:464
    Is it just because the form is *CALLED* WP? Have you tried it with
    something like EM, where the form is called EMC?
    
    Graham
950.2New menu form acts via DEFAULTCESARE::EIJSAll in 1 PieceMon Jun 29 1992 10:1324
    
    Sjaak,
    
    The 'Guide' (V3.0, Chapter 6.2 (sorry, no page, I'm using the
    Bookreader) states:
    
    	- If the menu doesn not contain the /CAPTIVE qualifier, search the
          Named Data of the Default form
    
    	- If the menu does not contain the /CAPTIVE qualifier, treat the user
          input as a form name and pass it as a parameter to the FORM
          function.
    
    <FORM EMC /CAPTIVE creates a new menu stack. Option TR puts you in a
    new menu form, which doesn't contain the /CAPTIVE. So, WP is then
    processed either via DEFAULT or as a FORM name.
    
    The same for <FORM FD/CAPTIVE (also in V3.0), where C (Create) puts you
    in a new menu form.
    
    HTH,
    
    	Simon
950.3More ...UTRTSC::BOSMANWe&#039;re just sugar mice in the rainMon Jun 29 1992 10:5624
    Hi,
    
�   Is it just because the form is *CALLED* WP? Have you tried it with
�   something like EM, where the form is called EMC?
    
    No, yes.
    
�   - If the menu does not contain the /CAPTIVE qualifier, treat the user
�     input as a form name and pass it as a parameter to the FORM
�     function.
    
    Should that be 'If the menu does contain ...'?
        
�   <FORM EMC /CAPTIVE creates a new menu stack. Option TR puts you in a
�   new menu form, which doesn't contain the /CAPTIVE. So, WP is then
�   processed either via DEFAULT or as a FORM name.
    
    Thus a user can bypass the /CAPTIVE by invoking a new menu and /CAPTIVE
    is *only* valid for the current menu. Is it logical then to say that
    the programmer should add /CAPTIVE to any menu following the first
    /CAPTIVE?
    
    Thanks for any help,
    Sjaak.
950.4No mistakeCESARE::EIJSAll in 1 PieceMon Jun 29 1992 13:0416
    
    Sjaak,
    
    > Should that be 'If the menu does contain ...'?
    
    No, I don't think so. Using both form names and menu options (as
    specified in DEFAULT) are ignored if the menu is called with /CAPTIVE
    (E.g. <FORM FD/CAPTIVE -> EM (ignored), EMC1 (ignored)). 
    
    If the user can get to a new menu from the /CAPTIVE menu, the /CAPTIVE
    seems not to go along. So, it seems that any followng menu form should
    be called with /CAPTIVE. Now that's going to be a lot of work...
    
    Ciao,
    
    	Simon
950.5Topic closedUTRTSC::BOSMANWe&#039;re just sugar mice in the rainMon Jun 29 1992 13:174
    Sorry Simon, I should have read that twice. (Ofcourse) your right.
    
    Thanks for the clarification,
    Sjaak.
950.6You've got it right!WAYLND::HOWARDOur business is computers not moneyTue Jun 30 1992 22:007
    What you are seeing is expected behavior.  Somewhere there is or was a
    caution about this.  All the user has to do is find a menu option to
    get him to a menu without /CAPTIVE, and he is no longer captive.  All
    /CAPTIVE does is to prevent ALL-IN-1 from looking for a form with that
    name in an open form library.
    
    Ben
950.7No Default options eitherSHALOT::NICODEMAvoid traffic; leave work at noonWed Jul 01 1992 17:1610
	RE: .-1

�   All /CAPTIVE does is to prevent ALL-IN-1 from looking for a form with that
�   name in an open form library.

	Actually, it does more than that.  It also removes the search of the
Default form when trying to match the option.  So you're basically limited to
options on the current menu (or extensions thereof, create by .MORE or /MORE).

	F