Exit button problem

At the end of my Captivate 2 project I have viewers click the
X (exit ) button on the Captivate skin to exit. Sometimes it works
and sometimes it doesn't. Couldn't find any settings. Any ideas?
Thanks! Tom

I am experiencing the same issue. For security support
reasons, I've been asked to convert my *.EXE training modules to
Web-based *.SWF. All the exit/close buttons in the EXEs work
correctly. Switching to SWF, the Player X(Close) button is inactive
and any created Exit Buttons do not properly close their respective
modules. Using the SWF Exit Buttons results in a display of an
empty frame which provides no means to close and a manually close
of the IE window must be used. Current environment (Captivate 2
development, IE 6 Browser w/Flash 9 plugin).
I have read all the posts that I can find on this issue and
have even tried JavaScript as a get around without success. I'm at
a lost as to find an appropriate solution. My days using EXE are
numbered.
Thanks. Bob

Similar Messages

  • Problem activating the back and exit button with the ALV using OO

    I have wrote my first alv using Methods.My problem is that i can't activete the BACK and  EXIT button in the standart toolbar .
    Look my code please .....
    Without PF-STATUS can i do it ?
    *& Report  YDP_DOUBLE_ALV
    REPORT  YDP_DOUBLE_ALV.
    TABLES : YQM_CERT , MARA , YOUTPUT_APPL.
    DATA : ALV_GRID TYPE REF TO CL_GUI_ALV_GRID,
           CUSTOM_CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER,
           FIELD_CAT TYPE LVC_T_FCAT,
           LAYOUT TYPE LVC_S_LAYO.
    DATA : ALV_GRID2 TYPE REF TO CL_GUI_ALV_GRID,
           CUSTOM_CONTAINER2 TYPE REF TO CL_GUI_CUSTOM_CONTAINER.
    *       FIELD_CAT TYPE LVC_T_FCAT,
    *       LAYOUT TYPE LVC_S_LAYO.
    DATA: DYNNR TYPE SY-DYNNR,
          REPID TYPE SY-REPID.
    DATA: OK_CODE TYPE SY-UCOMM.
    DATA : BEGIN OF ITAB OCCURS 0.
            INCLUDE STRUCTURE YQM_CERT.
    DATA   END OF ITAB.
    DATA : BEGIN OF ITAB1 OCCURS 0.
            INCLUDE STRUCTURE YOUTPUT_APPL.
    DATA   END OF ITAB1.
    *  MODULE DISPLAY_ALV OUTPUT
    MODULE DISPLAY_ALV OUTPUT.
      SET PF-STATUS 'ZST9'.
      PERFORM DISPLAY_ALV.
    ENDMODULE.                    "DISPLAY_ALV OUTPUT
                       "DISPLAY_ALV OUTPUT
    *& Module USER_COMMAND_0100 INPUT
    * text
    MODULE USER_COMMAND_0100 INPUT.
      CASE OK_CODE.
        WHEN 'BACK'.
          LEAVE TO SCREEN 0.
        WHEN 'EXIT'.
          LEAVE PROGRAM.
      ENDCASE.
    ENDMODULE. " USER_COMMAND_0100 INPUT
    START-OF-SELECTION.
      LAYOUT-ZEBRA = 'X'.
      LAYOUT-GRID_TITLE = 'YQM_CERT'.
      LAYOUT-CWIDTH_OPT = 'X'.
      LAYOUT-SMALLTITLE = 'X'.
      SELECT  * FROM  YQM_CERT INTO ITAB.
        APPEND ITAB.
      ENDSELECT.
      SELECT  * FROM  YOUTPUT_APPL INTO ITAB1.
        APPEND ITAB1.
      ENDSELECT.
      CALL SCREEN 100.
    END-OF-SELECTION.
    *&      Form  DISPLAY_ALV
    *       text
    FORM DISPLAY_ALV.
      IF ALV_GRID IS INITIAL.
        CREATE OBJECT CUSTOM_CONTAINER
          EXPORTING
    *      PARENT                      =
            CONTAINER_NAME              = 'CC_ALV'
    *       style                        =
    *      LIFETIME                    = lifetime_default
          REPID                       = REPID
          DYNNR                       = DYNNR
    *      NO_AUTODEF_PROGID_DYNNR     =
    *    EXCEPTIONS
    *      CNTL_ERROR                  = 1
    *      CNTL_SYSTEM_ERROR           = 2
    *      CREATE_ERROR                = 3
    *      LIFETIME_ERROR              = 4
    *      LIFETIME_DYNPRO_DYNPRO_LINK = 5
    *      others                      = 6
        IF SY-SUBRC <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        CREATE OBJECT ALV_GRID
          EXPORTING
    *    I_SHELLSTYLE      = 0
    *    I_LIFETIME        =
            I_PARENT          = CUSTOM_CONTAINER
    *    I_APPL_EVENTS     = space
    *    I_PARENTDBG       =
    *    I_APPLOGPARENT    =
    *    I_GRAPHICSPARENT  =
    *    I_NAME            =
    *    I_FCAT_COMPLETE   = SPACE
    *  EXCEPTIONS
    *    ERROR_CNTL_CREATE = 1
    *    ERROR_CNTL_INIT   = 2
    *    ERROR_CNTL_LINK   = 3
    *    ERROR_DP_CREATE   = 4
    *    others            = 5
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        CALL METHOD ALV_GRID->SET_TABLE_FOR_FIRST_DISPLAY
          EXPORTING
    *      I_BUFFER_ACTIVE               =
    *      I_BYPASSING_BUFFER            =
    *      I_CONSISTENCY_CHECK           =
             I_STRUCTURE_NAME              = 'YQM_CERT'
    *      IS_VARIANT                    =
    *      I_SAVE                        =
    *      I_DEFAULT                     = 'X'
           IS_LAYOUT                     = LAYOUT
    *      IS_PRINT                      =
    *      IT_SPECIAL_GROUPS             =
    *      IT_TOOLBAR_EXCLUDING          =
    *      IT_HYPERLINK                  =
    *      IT_ALV_GRAPHICS               =
    *      IT_EXCEPT_QINFO               =
    *      IR_SALV_ADAPTER               =
          CHANGING
            IT_OUTTAB                     = ITAB[]
    *      IT_FIELDCATALOG               =
    *      IT_SORT                       =
    *      IT_FILTER                     =
    *    EXCEPTIONS
    *      INVALID_PARAMETER_COMBINATION = 1
    *      PROGRAM_ERROR                 = 2
    *      TOO_MANY_LINES                = 3
    *      others                        = 4
        IF SY-SUBRC <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
      ELSE.
        CALL METHOD ALV_GRID->REFRESH_TABLE_DISPLAY
    *       EXPORTING
    *         IS_STABLE      =
    *         I_SOFT_REFRESH =
    *       EXCEPTIONS
    *         FINISHED       = 1
    *         others         = 2
        IF SY-SUBRC <> 0.
    *      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
      ENDIF.
    ENDFORM.                    "DISPLAY_ALV

    Hi
    U need  to active them in your status ZST9.
    Max

  • Lightroom problem with the exit button...

    In Lightroom, the window got redesigned in such a way that you can't move the cursor to the absolute top right corner and click to exit like you can in standard windows--you have to aim with the cursor on the exit button which is annoying.

    Just stumbled over the thread.
    Interesting how these discussions evolve.
    Someone points out an unexpected behavior. LR doesn't act conform with every other app on pc. Instead of accept this, people start argueing whether it is necessary to close apps in general, bla bla.
    Why not admit: Yes there is a flaw. There are workarounds, so it's not a deal breaker. We would like to have this addressed by adobe in the next version. It doesn't matter if there are users that never use the cross to close apps. It doesn't matter if there are other ways to close.
    Why change standards? This may be unintentionally here but there are other examples.
    The crop tool in LR.
    The Keyboard shortcuts. In every Adobe Application. I never understood, why there are no 2 adobe-apps that share the same shortcuts. Even standards like ctrl-ins/shift-ins does not work in for exyample in indesign. Drives me nuts. No, I don't want to use use ctrl-c/ctrl-v. I use my mouse with my left hand.
    Copy settings in LR. Ctrl-Shift-C. No other app uses this.
    Why change established standards??

  • Exit button not working in MS Explorer

    Hi. The exit button in our Captivate courses are not working
    all of a sudden. They work in FireFox but in MS IE. We are using
    Capivate 2.0. IE version is 6.0.

    Hi Apparo,
    In onAction method of the Exit button, a call is made to the TargetExitApplication as follows:
    fpm.navigate(wdThis
    .wdGetFcNavigationInterface()
    .getNavigationTargetExitApplication());
    Also, the Exit button does work in the Address Overview/Edit/Review Page, but not in W-4 Tax and Benefits Enrollment.
    Any help on this problem !!!
    Regards,
    Adren

  • Exit Button not working in ESS

    Hi All,
    We have configured ESS in our landscape. When I go to any Overview/Edit/Review Page (in W-4 Tax, Add/Change dependents etc..), the Exit button which is present is not working. When I click the Exit button, it doesn't exit the current view,  but instead stays at the current location.
    Can anyone tell me the reason for this strange behaviour? Also, where should I make the code level changes for the Exit button work.
    Any kind of help would be greatly appreciated.
    Regards,
    Adren

    Hi Apparo,
    In onAction method of the Exit button, a call is made to the TargetExitApplication as follows:
    fpm.navigate(wdThis
    .wdGetFcNavigationInterface()
    .getNavigationTargetExitApplication());
    Also, the Exit button does work in the Address Overview/Edit/Review Page, but not in W-4 Tax and Benefits Enrollment.
    Any help on this problem !!!
    Regards,
    Adren

  • Exit Button script won't work in Adobe Reader 8

    Hello,
    I have this code on Exit button for pdf form:
    app.execMenuItem("Close");
    Or
    to give warning before Exit: Have a second RealExit Button hidden to execute the code
    var answer = xfa.host.messageBox("Are you sure you want to Exit?","Warning Message",2,1);
    if(answer==1){
    RealExit.execEvent('click');
    I tried both the code one at a time but no luck in Adobe Acrobat Version 8, works like a charm in Adobe Acrobat 9
    I would like the user to click the Exit button if they choose to exit. However it doesn't work in Adobe Acrobat 8 but works in 9 version. Is there a work around? Any suggestions???
    Thanks

    This answer may not be a big help but sure will give you some level of understanding....
    Check the URL>>>http://kb2.adobe.com/cps/402/kb402673.html
    Check the section "PDF Forms-related issues:" starting mid page.....
    Not all releases/versions are good. Some releases tend to have some bugs...the version you tested could be one of them. Adobe always recommends to be on the latest version. If client still on older version that is client's problem especially there should not be any restrictions on upgrading to Latest version when the software is free!

  • Exit button not working in Captivate 7 published output

    Hi. I am using Capivate v7 and am experiecing this problem with published output:
    I am using an Exit button that runs the standard javascript code
         javascript:window.close()
    so that the user can exit the presentation. The button works fine when I test out the presentation using Internet Explorer 8, but when I generate an output and try running the .swf file, the button does not work.
    How do I get an Exit button to work for the .swf output?
    Thanks,
    - Michael Fekete

    Yes, the close X does work 100% of the time. That's because the browser itself is just a window in the operating system. And you are commanding the window to close.
    And you might find yourself asking why that would work while the Exit button fails. And it would be that it's a security issue. Security prevents the window from closing because if a web site was nefarious, it could actually trap you by making changes and quickly closing the window and preventing you from browsing elsewhere.
    It's simple to turn off the Exit button. Just click Project > Skin Editor and clear the Close checkbox.
    Cheers... Rick

  • Exit button not working in Safari

    Has anyone run into this, specifically with Safari? I created a module in Captivate 8, that has a close button on the skin. The module has been uploaded to my clients LMS and it closes no problem on all other browsers except Safari. I tried creating a button on the last page of the slide as well with the "exit" action and that doesn't seem to work either in Safari. Does anyone have an idea how to fix this issue?

    I tried an Exit button (clickbox associated with the action Exit).  It freezes Safari for about 10-15 seconds and then finally closes the browser tab.

  • Exit Button not working through Workflow

    Hi,
    I'm using a Custom Business Object for triggering my workflow. I've used own transaction and used in my method. The workflow triggers and works properly. My problem is when i run the transaction code manually and click on 'Back' or 'Exit' button, it leaves program and comes out. But when i go through the workflow and execute from my inbox, it doesn't come out of the tcode i.e it doesn't leaves the program. It remains in the same screen...
    Can anyone know what is the problem ??
    Do i need to end the event  or something have to be done for exit ?

    You wouldn't happen to have a loop there, and steps that continue within a dialogue session, so it is actually new workitems you keep executing?
    Perhaps not, so the problem may be caused by the way you are calling the code that presents the user interface. When you submit a program and the program tries to leave the screen it will go to the screen it came from. But it didn't really come from a screen. I believe that may be your problem in this case.
    For a synchronous task I would recommend calling a function module - the function module can open a screen, or do whatever you need. The main point is that the function module can return a value to the method which can be used to determine whether you should call the macro exit_cancelled to indicate that the user cancelled execution.

  • ESS - Time Accounts- Exit button not working

    We have implemented ESS Business Package, the Time Accounts application's Exit button is not working.
    When we click on Exit, it is not doing anything. In Development env it is working fine, but when it comes to quality it is not working.
    suggest me if we can solve this problem.

    Hi Kiran,
    We had a same problem with "Exit" button for "Benefits Enrollment" in both dev and quality systems. As a workaround we redirected to the specific iView using WDPortalNavigation.navigateAbsolute on clicking "Exit  button".
    Hope this helps.
    Regards,
    Adren

  • Cancel and Exit button not working

    Dear Experts,
    <u>Cancel and Exit button not working</u>
    I am calling a screen from inside a report program
    using SET SCREEN 9000.
    2 of the date fields(start date end date)
    on this screen are Mandatory.
    I am not able to Come out of this screen 9000 using
    CANCEL or EXIT button
    without giving a date entry in both of
    Mandatory fields (start date end date).
    Can someone help me with a solution?
    Appreciate your valuable help;
    Points assured
    Thanks,
    Aby Jacob

    Hi..
    To avoid this problem you have to use AT EXIT-COMMAND Module.
    1. In the GUI Status for both EXIT and CANCEL buttons assign the Function type E (Exit Command)
    2. In the PAI of the Screen Call this module.
       MODULE EXIT_SCREEN AT EXIT COMMAND.
    3. Now check the OK_CODE or Sy-ucomm in this module to Leave the Screen
       MODULE EXIT_SCREEN  INPUT.
           CASE OK_CODE.
          WHEN 'EXIT' .
                LEAVE TO SCREEN 0.
          WHEN 'CANCEL'.
          ENDCASE.
       ENDMODULE.
    This will surely work.
    <b>reward if Helpful.</b>

  • The "Exit" button is not working on my LMS

    The "Exit" button in Captivate doesn't work once the course is uploaded to my LMS (Meridian).  Any ideas what the problem might be?  All the other buttons in the course work as advertised once uploaded.
    Thanks.
    Jay

    You have identified the problem. If you have Warranty or AppleCare coverage, make Genius reservation and take or send to Apple for resolution. Troubleshoot. When iPhone 5 is open, the home button contacts are present right there. With volt meter placed on home flex you can see if pressing home button completes the circuit. You can bridge the dock home button contacts and see if it actually causes response in the iPhone. If not dock or its contacts are faulty or logic board is faulty.

  • Course will not play in LMS until the Exit button is clicked

    I'm stumped.  I've created a course that plays fine until I enable reporting in our LMS.  This is the first course we've created in Captivate 5, and I'm using the same Quiz Reporting settings that we used in Captivate 4 (that always worked).  If the course is published to the LMS without quiz reporting enabled, the course plays fine.
    However, if the course is published to the LMS with Quiz Reporting enabled, then the course freezes on the first slide, and will not play until the Exit Button in the playback controls is clicked.  All of the other buttons cease to function until the exit button is clicked as well.
    Any ideas on what could be causing this?

    Just a quick update... I was able to resolve our issue.
    (in case anybody else runs into this issue, maybe this will help)
    We were using AICC to report back to our LMS (Saba) and it's always caused various kinds of problems with Captivate v4.  We were using some sort of work around to get the reporting to work properly.  I was trying to use the same work around we used in v4 with v5, which (I'm totally guessing here) was what was causing the problem.
    Instead of using AICC, I uploaded a SCORM package to our LMS, and everythings been working great since.

  • EXIT button on the top level form is not working.

    Hi I have 10g forms deployed on the web.
    On the top level form, there is a exit button on it.
    And for this form, under ALERTS I have two alerts viz. QUIT_ALERT and BANNER_ALERT.
    Now when I press the EXIT button on the form, nothing is happening. Neither prompting the ALERT nor closing the FORM.
    Where and What could be the problem??
    I have the following code for the exit button
    IF G$_DISPLAY_ALERT('QUIT_ALERT','Do you really wish to quit?') = ALERT_BUTTON1 THEN
    EXIT_FORM;
    END IFAnd the function G$_DISPLAY_ALERT has following code
    FUNCTION G$_DISPLAY_ALERT(ALERT_NAME IN VARCHAR2,
    MSG_STRING IN VARCHAR2) RETURN NUMBER IS
    ALERT_ID ALERT;
    AL_NAME VARCHAR2(30);
    ALERT_BUT NUMBER;
    BEGIN
    IF ALERT_NAME IS NULL THEN
    AL_NAME := 'G$_WARNING_ALERT';
    ELSE
    AL_NAME := ALERT_NAME;
    END IF;
    ALERT_ID := FIND_ALERT(AL_NAME);
    IF ID_NULL(ALERT_ID) THEN
    RAISE FORM_TRIGGER_FAILURE;
    END IF;
    SET_ALERT_PROPERTY(ALERT_ID, ALERT_BUT, MSG_STRING);
    ALERT_BUT := SHOW_ALERT(ALERT_ID);
    RETURN ALERT_BUT;
    END;Edited by: Charan on Mar 30, 2011 2:01 PM

    seems like some trigger is firing, because i'm getting a CAUTION popup now saying Please Acknowledge.Actually, the PAUSE() built-in is what brings up the "Please Acknowledge" alert. Clearly, your trigger is firing so there must be something wrong with either your WBP trigger code or your G$_DISPLAY_ALERT program unit.
    Try the same technique on your program unit. I would also suggest you display a message in your Exception handler. My guess is that your function is failing but since you don't report the failure, it appears that your code runs successfully.
    FUNCTION G$_DISPLAY_ALERT(ALERT_NAME IN VARCHAR2,
                          MSG_STRING IN VARCHAR2) RETURN NUMBER IS
       ALERT_ID         ALERT;
       AL_NAME          VARCHAR2(30);
       ALERT_BUT        NUMBER;
    BEGIN
       Message('Alert_name: '||ALERT_NAME);
       PAUSE;
    IF ALERT_NAME IS NULL THEN
       AL_NAME := 'G$_WARNING_ALERT';
    ELSE
       AL_NAME := ALERT_NAME;
    END IF;
    ALERT_ID := FIND_ALERT(AL_NAME);
    IF ID_NULL(ALERT_ID) THEN
       Message('Unable to find Alert: '||ALERT_NAME);
       Message('Unable to find Alert: '||ALERT_NAME);
       RAISE FORM_TRIGGER_FAILURE;
    END IF;
    SET_ALERT_PROPERTY(ALERT_ID, ALERT_BUT, MSG_STRING);
    ALERT_BUT := SHOW_ALERT(ALERT_ID);
    RETURN ALERT_BUT;
    END;Then you can see what the value of ALERT_NAME is and verify your code is executing as expected.
    Craig...
    Edited by: CraigB on Mar 30, 2011 12:54 PM

  • Exit button doesn't work

    On .swf files, the Exit button in the skin doesn't close the
    file (it works just fine if the file is .exe). All the other
    buttons work fine. Any ideas?

    Hi, I know this issue was a long time ago, but I am experiencing the same problem with a course that has been loaded into the LMS, the exit/close button on the playbar isn't working.  I am using Captivate 5.  I have published using AICC rather than SCORM, as there were some issues with the passing over of scores from the e-learning programme I'd built to the LMS which were resolved by using AICC.  The close/exit button however did work when it was originally published using SCORM!
    I'm considering just removing the exit/close button on the programme and putting a message at the start and at the end to say just close browser window to exit the programme.
    I'd be very grateful if anyone could advise if there is anything else anyone could recommend trying?
    Thank you
    Sarah

Maybe you are looking for