Unloading a Module via an exit button on Window component

This is a Flex 4 project.
I have a module create with MXML.
The module uses the window component.
How do I use the "x" (exit button) on the window component to unload the module?
This is part of my code on the main application:
    private function displayModule( moduleURL:String ):void
                if( moduleLoader.url != moduleURL )
                    moduleLoader.url = moduleURL;
<s:Button x="23.35" y="50.85" label="1a" width="50" height="50" id="A1" click="displayModule('windowA1.swf');"/>
<mx:ModuleLoader id="moduleLoader" width="100%" height="100%"  x="150" y="25"/>
Thanks for any help

Grab some event when the X button is clicked and set the moduleLoader.url =
null

Similar Messages

  • How To Use a Custom Close Button In Window Component

    Hello,
    I have a window component, with the default close button
    turned off, and a new custom close button added to the movie clip
    that is displayed inside the window component. How do I get a click
    on the close button to close the window?
    This is the code I currently have to create the window (and
    the listeners to close the window using the default close button):

    basicalyyou have to use
    myWindow.deletePopUp();
    if my memory serves the content mc is loaded into a mc called
    contentHolder, inside the window component, so
    if you are referencing the window from the scope of your
    loaded mc it will be
    this._parent._parent.deletePopUp();
    or if from the button's scope
    this._parent._parent._parent.deletePopUp();
    try traceing the parantage down til you hit the window.

  • Juz a question on exit button actionlistener

    hi all.. i'm just wondering whether is it possible to create an exit button when its function would exit the program or close a window.
    for example, when i click on the exit button, the window should close juz like the 'X' at the top of the window.
    much appreciated..=)

    // Inside the JFrame or JDialog you need to close:
    btnCloseWindow.addActionListener(new ActionListener() {
         public void actionPerformed(ActionEvent ev) {
              dispose();
    });

  • Profiling the loading and unloading of modules

    Modules appear to be the ideal solution for building complex rich internet applications but first hand experience has also shown me that they can leak memory like nothing else. I've read anything and everything I could find about modules and module loading/unloading including of Alex Harui's blog post "What We Know About Unloading Modules" that reveals a number of potential leak causes that should be considered.
    I've now created a simple soak test that repeatedly loads and unloads a specified module to help identify memory leaks using the profiler. However, even with the most basic of modules, I find that memory usage will steadily grow. What I'd like to know is what memory stuff is unavoidable flex overhead associated with the loading of modules and what memory stuff am I guilty for, for not cleaning up object references? I'd like to be able to establish some baseline values to which I will be able to compare future modules against.
    I've been following the approach suggested in the Adobe Flash Builder 4 Reference page "Identifying problem areas"
    "One approach to identifying a memory leak is to first find a discrete set of steps that you can do over and over again with your application, where memory usage continues to grow. It is important to do that set of steps at least once in your application before taking the initial memory snapshot so that any cached objects or other instances are included in that snapshot."
    Obviously my set of discrete steps is the loading and unloading of a module. I load and unload the module once before taking a memory snapshot. Then I run my test that loads and unloads the module a large number of times and then take another snapshot.
    After running my test on a very basic module for 200 cycles I make the following observations in the profiler:
    Live Objects:
    Class
    Package (Filtered)
    Cumulative Instances
    Instances
    Cumulative Memory
    Memory
    _basicModule_mx_core_FlexModuleFactory
    201 (1.77%)
    201 (85.17%)
    111756 (24.35%)
    111756 (95.35%)
    What ever that _basicModule_mx_core_FlexModuleFactory class is, it's 201 instances end up accounting for over 95% of the memory in "Live Objects".
    Loitering Objects:
    Class
    Package
    Instances
    Memory
    Class
    600 (9.08%)
    2743074 (85.23%)
    _basicModule_mx_core_FlexModuleFactory
    200 (3.03%)
    111200 (3.45%)
    However this data suggests that the _basicModule_mx_core_FlexModuleFactory class is the least of my worries, only accounting for 3.45% of the total memory in "Loitering Objects". Compare that to the Class class with it's 600 instances consuming over 85% of the memory. Exploring the Class class deeper appears to show them all to be the [newclass] internal player actions.
    Allocation Trace:
    Method
    Package (Filtered)
    Cumulative Instances
    Self Instances
    Cumulative Memory
    Self Memory
    [newclass]
    1200 (1.39%)
    1200 (14.82%)
    2762274 (13.64%)
    2762274 (62.76%)
    This appears to confirm the observations from the "Loitering Objects" table, but do I have any influence over the internal player actions?
    So this brings me back to my original question:
    What memory stuff is unavoidable flex overhead associated with the loading of modules and what memory stuff am I guilty for, for not cleaning up object references? If these are the results for such a basic module, what can I really expect for a much more complex module? How can I make better sense of the profile data?
    This is my basic module soak tester (sorry about the code dump but there's not that much code really):
    basicModule.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Module xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/halo"
               layout="absolute" width="400" height="300"
               backgroundColor="#0096FF" backgroundAlpha="0.2">
         <s:Label x="165" y="135" text="basicModule" fontSize="20" fontWeight="bold"/>
    </mx:Module>
    moduleSoakTester.mxml
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                   xmlns:s="library://ns.adobe.com/flex/spark"
                   xmlns:mx="library://ns.adobe.com/flex/halo"
                   width="400" height="300" backgroundColor="#D4D4D4"
                   initialize="application_initializeHandler(event)">
         <fx:Script>
              <![CDATA[
                   import mx.events.FlexEvent;
                   import mx.events.ModuleEvent;
                   [Bindable]
                   public var loadCount:int = -1;
                   [Bindable]
                   public var unloadCount:int = -1;
                   public var maxCycles:int = 200;
                   public var loadTimer:Timer = new Timer(500, 1);
                   public var unloadTimer:Timer = new Timer(500, 1);
                   protected function application_initializeHandler(event:FlexEvent):void
                        loadTimer.addEventListener(TimerEvent.TIMER_COMPLETE, loadTimer_timerCompleteHandler);
                        unloadTimer.addEventListener(TimerEvent.TIMER_COMPLETE, unloadTimer_timerCompleteHandler);
                   protected function loadModule():void
                        if(loadCount < maxCycles)
                             moduleLoader.url = [correctPath] + "/basicModule.swf";
                             moduleLoader.loadModule();
                             loadCount++;
                   protected function unloadModule():void
                        moduleLoader.unloadModule();
                        unloadCount++;
                   protected function load_clickHandler(event:MouseEvent):void
                        load.enabled = false;
                        loadModule();
                        unload.enabled = true;
                   protected function unload_clickHandler(event:MouseEvent):void
                        unload.enabled = false;
                        unloadModule();
                        run.enabled = true;
                   protected function run_clickHandler(event:MouseEvent):void
                        run.enabled = false;
                        moduleLoader.addEventListener(ModuleEvent.READY, moduleLoader_readyHandler);
                        moduleLoader.addEventListener(ModuleEvent.UNLOAD, moduleLoader_unloadHandler);
                        loadTimer.start();
                   protected function moduleLoader_readyHandler(event:ModuleEvent):void
                        unloadTimer.start();
                   protected function moduleLoader_unloadHandler(event:ModuleEvent):void
                        loadTimer.start();
                   protected function loadTimer_timerCompleteHandler(event:TimerEvent):void
                        loadModule();
                   protected function unloadTimer_timerCompleteHandler(event:TimerEvent):void
                        unloadModule();
              ]]>
         </fx:Script>
         <mx:ModuleLoader id="moduleLoader"/>
         <s:VGroup x="20" y="20">
              <s:HGroup>
                   <s:Button id="load" label="Load" click="load_clickHandler(event)" enabled="true"/>
                   <s:Button id="unload" label="Unload" click="unload_clickHandler(event)" enabled="false"/>
                   <s:Button id="run" label="Run" click="run_clickHandler(event)" enabled="false"/>
              </s:HGroup>
              <s:Label text="loaded: {loadCount.toString()}" fontSize="15"/>
              <s:Label text="unloaded: {unloadCount.toString()}" fontSize="15" x="484" y="472"/>
         </s:VGroup>
    </s:Application>
    Cheers,
    -Damon

    Easiest way I've found to get your SDK version from within Builder is to add this: <mx:Label text="{mx_internal::VERSION}" />
    http://blog.flexexamples.com/2008/10/29/determining-your-flex-sdk-version-number/
    Peter

  • Exit button not working in exe file made with Aggregator

    Hi,
    I created an .exe file using Aggregator in full screen mode but the exit button on the skin doesn't work. When I click the exit button, the dislay hiccups (wobbles a bit) but the file keeps playing and doesn't close. This is especially problematic since this occurs in full screen. The only way to exit is by hitting the Escape key on the keyboard. The exit button works fine in individual .exe files of the modules; it's just in the aggregated .exe file that the exit button doesn't work. Is there anything special I need to do to make the exit button work with Aggregator?

    Hi, this is more J2EE related stuff, SAP came with a solution but is taking ages to get the next page after the "Exit" button is pushed:
    Go to VisualAdnmin >server(n) >Services >Configuration Adapter >
    (Right side Pane) webdynpro >sap.com >tcwddispwda >PropertySheet
    default.
    Edit the property sheet and change the custom value for the property
    "sap.locking.maxWaitInterval" to 200.
    Note 1113811, explains why these kind of errors happen.
    I still waiting for a better solution from SAP.
    Cheers

  • MODULE USER_COMMAND_0200 AT EXIT-COMMAND.

    Hi Experts,
    I knew that the following statements allows user to by pass all the screen validations, so to achieve this we have to declare a function code in SET PF-STATUS of type Exit Command. So, my doubts r,
    1- Anyway, we r adding the AT EXIT-COMMAND as a suffix to to Module statement, so again What is the necessity declaring in the SET PF-STATUS as a function code?
    PROCESS AFTER INPUT.
       MODULE USER_COMMAND_0200 AT EXIT-COMMAND.
    2- What else wuld do the above statement apart from overcoming the validations(coz the author has mentioned this statement - ''An Exit-command allows you to insert functionality into the PAI that by passes all screen validation '', Which is I dont understand!)?
    ThanQ.

    hi Srinivas,
    Let us consider the following example:
    If a user wants to exit a screen, by clicking the BACK button, he should be taken out ..right?
    Instead, should there be a message poping up saying "Mandatory fields are not entered".. or "enter character data in name field"...ect..?
    no...hence, to ignore these validation, we put the code to exit the screen in a module. This module has to be defined with ...AT EXIT-COMMAND extension.
    Hope this answers your question.
    Sajan Joseph.

  • To perform database update in a module with AT EXIT-COMMAND addition

    Dear All,
    I have a function code 'EXIT' with function type 'E'. When this function code is triggered, my screen should close.
    In the module that handles this function code (defined with AT EXIT-COMMAND addition), I will prompt the user whether he/she want's to save the data before exiting with the POPUP_TO_CONFIRM_STEP function module. The text message in the dialog box is "Do you want to save before exiting?".
    When the user wants to save the data, a simple UPDATE statement will be executed to write the data on screen to database.
    The problem here is since the module is defined with AT EXIT-COMMAND addition, the data on screen won't be copied to their corresponding variable on the code (correct me if I'm wrong). Therefore, even though database update is performed, the data written to database are no different that the original.
    How to perform database update in a module with AT EXIT-COMMAND addition?
    or
    Is it even a "custom" or a "good practice" to prompt user to save data before exiting?
    Thanks in advance,
    Haris

    With an exit command, if there's anything that would be lost, I would prompt "Data will be lost, do you wish to continue?". If they do, the database is not updated, if they don't, they stay in the transaction.
    This is because the exit command runs before validation. So how can you know the data is correct?
    If you have a button to leave the transaction that isn't an exit command, then you could prompt to save instead. There the choices should be - quit without saving, save and quit, don't quit.
    Doing a database update in an exit command is not a good idea.
    matt
    Edited by: Matt on Mar 15, 2011 11:53 AM

  • Exit button code not working in published captivate file

    Hi,
    I have created a elearning module in captivate 8. I have an exit button at the end of the module. The button has the inbuilt code ''on success - exit''. When I publish this file to swf or AICC format, this exit button doesnot work. Please help!

    have you confirmed that this javascript code ( only
    javascript code in html, no swf) works?
    in some cases the window.close() statement works only for
    popup windows. so make sure of it.

  • 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.

  • Custom Exit Button not working..looks for required input field on screen?

    I defined this EXIT button as type E in Menu Painter.
    I am using "MODULE At EXIT-COMMAND" in my PAI.
    SAP message still asks for the required input field when I select the function EXIT button?
    The logic still will not break into the At EXIT-COMMAND of my PAI?
       Thank-You.

    Hi
    Have you assigned variable OK_CODE in the list of screen element?
    IF NOT zin_railid is initial.
        LEAVE TO SCREEN 0100.
    ENDIF.
    Which is the sense to create a button for exit-command and doesn't allow the exit if the input field is empty?
    In SE41 I entered "Back" over the back button, "EXIT" over the exit button, and "CANCEL" over the cancel button.
    I selected each one, and got a popup to enter "E" for each type. As I said they appear, but do nothing?
    Did I need to set a status for these?
    No you don't, it's only important to define a functional having the attribute for EXIT-COMMAND
    Max
    Max
    Edited by: max bianchi on Nov 5, 2010 6:31 PM

  • 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.

  • 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>

  • Exit button in ABAP Webdynpro doesnot work with SPNEGO

    Dear Webdynpro Gurus,
    we are in weird situation where we have webdynpro application in ABAP with exit button.
    we have ABAP System and EP System and SSO configured for these two systems.
    We configured EP system with Microsoft Active directory for single-signon with SPNEGO.
    this configuration is working fine.
    the situation is when we click on exit button, it is not redirecting to the main iview and there is no action taking place.
    please find the code for the exit button:
    *METHOD onactionexit .*
      *CONSTANTS lc_uri TYPE string VALUE 'ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles'.*
      *constants lc_url type string value '/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_employee_search'.*
    'ROLES://pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.pages/com.sap.pct.erp.ess.overview'.**
    *   Call New portal Page or iView**
      *TYPES: BEGIN OF navigation,*
        *target       TYPE string,*
        *mode         TYPE string,*
        *features     TYPE string,*
        *window       TYPE string,*
        *history_mode TYPE string,*
        *target_title TYPE string,*
        *context_url  TYPE string,*
       *END OF navigation.*
      *DATA: wa_navigation TYPE navigation.*
      *data : lv_url1 type string.*
      *DATA lo_api_component  TYPE REF TO if_wd_component.*
      *DATA lo_portal_manager TYPE REF TO if_wd_portal_integration.*
      *lo_api_component = wd_comp_controller->wd_get_api( ).*
      *lo_portal_manager = lo_api_component->get_portal_manager( ).*
      *concatenate lc_uri lc_url into lv_url1 respecting blanks .*
      *wa_navigation-target = lv_url1.*
      *wa_navigation-mode   = '0'.*
      *CALL METHOD lo_portal_manager->navigate_absolute*
        *EXPORTING*
          *navigation_target = wa_navigation-target*
          *navigation_mode   = wa_navigation-mode "IF_WD_PORTAL_INTEGRATION=>CO_SHOW_INPLACE*
          *post_parameters = ABAP_TRUE.*
    *ENDMETHOD.*
    Please help me to get out of this situation.
    Thanks & Regards,
    Khurshid.

    It is calling the workflow program exit before the SAP_WAPI_WORKITEM_COMPLETE function module.
    So closing the thread.

  • 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

  • Exit button issue in Captivate 5

    Hi,
    This is regarding the exit button on the playback controls. I have been using Captivate from version 2. Recently, started using version 5. When I published my simulation, the exit button is not working as earlier. It is also not working from- web server(IIS, Apache), when opened as pop-up as well. In local too however not working. I tried in both IE 7 and Firefox latest version.
    I have seen the response from Adobe on this issue on this forum. It was quite surprising; it did not talk about the solution at all;
    What I am not sure about is -
    1. Why the exit button was working earlier versions.. why is it not working in latest?
    2. Why should when simple code like top.close(); works fine (when coded inside the Captivate)?
    3. Why is Adobe not acknowledging the issue?
    4. Why there is no working around provided in the forums for this issue?
    Could anybody please help me understanding this problem? I am really frustrated.
    Thanks.

    Happy New to all as well!
    You are absolutely correct! The moment reporting is activated, the EXIT no longer functions. Although in my case, we are not using the time/slider bar but custom navigation buttons with an exit button on the last slide (and at the top of each slide).
    This whole EXIT button issue (not just Cp 5 but Cp 6 as well) is nearly bringing me to the point of tears! This is really ridiculous! I am in a tough position right now where my manager may be wondering if I am right person for this job because I cannot make a little EXIT button work in our lessons.
    "Solutions" or excuses that I have received
    - Just remove the EXIT button -- No, we use a standard corporate template which hundreds of employees are already familiar with. To remove the EXIT button and instruct the learner to just close the browser would be unacceptable and a rather inelegant way to exiting a lesson.
    - It is a tough issue that isn't Captivate's fault
      With all due respect to the awesome person who keeps stating that, I have a feeling that you have not used other rapid elearning tools. Building an EXIT button in all the other major elearning tools is easy and works every time.
    The source of my personal difficulty is that every other course that was built by previous developers (not using Captivate), all open in a child window and all have a working EXIT button.
    I believe the PRIMARY reason for this problem might be in the fact that... inexplicably... Captivate does not offer an option to start a lesson in a CHILD window (i.e. separate browser window). This is why no javascript in the world will allow the tab to close (e.g. EXIT button). Closing a tab or browser window via javascript only works when the same instance was previously opened by a script using the window.open method. In other words, you can only use the javascript method to close an instance that was spawned via javascript.
    This should explain why lessons published in Lectora (et al) always have working EXIT buttons every time and in every browser (minor exception is Opera for unrelated reasons).
    The second red box is just another one of my problems with Captivate 6 (not related to this topic).
    Solution????
    I've been racking my brain trying to modify Captivate's HTML/javascript in order to carry over the AICC (or SCORM - same process) variables into a child window.
    Like another participant stated, you can't simply rename the original index.html to index2.html and create a redirection like this:
    <script type="text/javascript">   
    window.open("index2.html","lesson","location=0,toolbar=0,status=0,resizable=1,width=975,he ight=600");</script>
    <body>
    Yes, I tried this as well... but unfortunately, it breaks the AICC to LMS connection. *BUT* I can promise one thing... using the above redirection, does guarantee that your EXIT button works every time! Pity the LMS connection breaks!
    QUESTION?
    Does anyone have advanced knowledge of javascript in order to code the INDEX.HTML to open the lesson in a child windows AND maintain a connection to the LMS?

Maybe you are looking for