You too can display non-modal dialog boxes: LrDialogs.presentFloatingDialog

Undocumented function: LrDialogs.presentFloatingDialog
ref: http://feedback.photoshop.com/photoshop_family/topics/sdk_lrdialogs_presentfloatingdialog_ and_showstringsdialog_undocumented
This works for displaying non-modal dialog box:
LrFunctionContext.postAsyncTaskWithContext( "test", function( context )
    local LrPhotoPictureView = import 'LrPhotoPictureView'
    local photo = catalog:getTargetPhoto()
    local pictureView = LrPhotoPictureView.makePhotoPictureView{
          width = 400, height = 400, photo = photo,
    local result = LrDialogs.presentFloatingDialog {
        title = "Thumbnail test",
        background_color = LrColor ("white"), -- required for (uncolored) static_text display, else inside of box is black and so can't see black text.
        contents = vf:column {
            vf:static_text {
                title = photo:getFormattedMetadata ("fileName"),
            pictureView,
            --vf:edit_field { - no sirve, presumably keystrokes are not trapped by box.
            --    bind_to_object = prefs,
            --    value = app:getGlobalPrefBinding( 'tempForTest' ),
            vf:push_button {
                title = "Click me",
                action = function( button )
                    app:show{ info="Pushed" } -- glorified call to LrDialogs.presentModalDialog - works.
                end,
    -- LrDialogs( app:getGlobalPref( 'tempForTest' ), result ) -- no sirve.
end )
Enjoy!
Rob

jarnoh wrote:
there is no way to activate previously opened dialog?
I assume that to be the case, and so it takes a moment to come up if there is much contents.
jarnoh wrote:
Doesn't seem to be really useful
For me, it would be very useful, if it was reliable, but so far, not so good.
UPDATE: Bug I thought was in non-modal dialog is also in modal dialog (scrolled_view must not be followed by another components in tabbed container - see comments in code below):
LrFunctionContext.postAsyncTaskWithContext( "tt", function( context )
    local props = LrBinding.makePropertyTable( context )
    props.tv = 0
    local vi = {
        vf:tab_view {
            vf:tab_view_item {
                identifier = "t1",
                title = "T1",
                vf:static_text {
                    title = "temp1"
            vf:tab_view_item {
                identifier = "t2",
                title = "T2",
                vf:scrolled_view {
                    vf:slider {
                        bind_to_object = props,
                        value = LrView.bind( 'tv' ),        
                -- with this here, Lr crashes after adjusting slider and then switching tabs - comment it out, and all is well:
                --vf:static_text {
                --    title = "this cant be here",
    LrDialogs.presentModalDialog {
        title = "test",
        contents = vf:view( vi )
end )
R
Message was edited by: Rob Cole

Similar Messages

  • How to display non modal dialog box in a Dll call from TestStand implemented in visual c

    Dear Jason F.
    Applications Engineer
    National Instruments
    Hello
    I did the same way you told me
    the non modal dialog appeared and
    system hangs and
    giving the error message
    ""SeqEdit.exe-Application Error
    The instruction at �0x047fc5b0� referenced memory at �0x047fc5b0�. The memory could not be �read� ""
    please solve my problem
    and thanks for yours early response
    you can email me at
    [email protected]

    Hi Mkehret,
    Does your dialog have ActiveX controls on it? If your DLL dialog uses ActiveX controls and is not programmed in a certain manner it can hang because of a conflict in the threading model used by the TestStand Engine that is calling into your DLL and the model that is required by the MFC ActiveX Container. If you are using ActiveX controls in your dialog, you need to make special considerations for the threading model MFC dialogs that use ActiveX controls need in order to work properly. The example under \Examples\MFCActiveXContainerDlg illustrates how to appropriately handle this situation as well as explaining why it is necessary.
    Note: The above example displays the dialog as modal, but this is irrelevant to the problem I am describing.
    Again for information on properly creating a dialog class object and displaying it as non-modal refer to the information on MSDN that I referred you to in this post:
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000E98A0000&USEARCHCONTEXT_CATEGORY_0=_8_&USEARCHCONTEXT_CATEGORY_S=0&UCATEGORY_0=_8_&UCATEGORY_S=0
    If your dialog does not use ActiveX controls or after trying the programming method illustrated in the "MFCActiveXContainerDlg" example TestStand still hangs when calling your DLL, try calling your DLL from another environment just to make sure whether the DLL works at all. If the DLL works properly when called by another environment (e.g. VB, VC++, LabVIEW, or CVI), please submit a MINIMAL and REPRODUCEABLE example source project for your DLL for us to look at (please exclude all unnecessary code not required to reproduce the specific problem of displaying the dialog, and include all files necessary to build your dll with any
    specific instructions needed to do so).
    Jason F.
    Applications Engineer
    National Instruments
    www.ni.com/ask

  • How to create non-modal dialog box?

    I'm trying to create a non-modal dialog box. The purpose is to show an alarm for the user but should leave the calling VI continuing to run. I have created such a thing -- the problem is that I can't figure out how to get the dialog box to go away! It stops running but the window just hangs around. See the attached VIs and image.
    Thanks in advance for your help,
    Chad
    Attachments:
    alarm_ui.png ‏11 KB
    alarm_ui-2.vi ‏11 KB
    message_to_user.vi ‏11 KB

    Ok, I've attached the files. Thanks for looking at this.
    Chad
    Attachments:
    alarm_ui-2.vi ‏11 KB
    message_to_user.vi ‏11 KB

  • Can't access Modal dialog box via Powershell script

    Hi,
    I have a powershell script to login to an IE website and everything works fine excepting when I call a modal dialog box.  I've attached the line where the modula dialog is invoked.  When it gets to this part the script hangs and I'm unable
    to get past this.  I've googled a few articles where it suggests I should run an a scheduled task to scrape for the modal dialog box but I've tried it without much luck.  If you can please give me some pointers on resolving this issue. 
    Thnx
    Sue.
    $ie.Document.getElementsByTagName("button") | ? { $_.innerText -eq 'UNLOCK User' } | Select-Object -first 1 | % { $_.Click() }
    Sue

    Hi,
    I have a powershell script to login to an IE website and everything works fine excepting when I call a modal dialog box.  I've attached the line where the modula dialog is invoked.  When it gets to this part the script hangs and I'm unable
    to get past this.  I've googled a few articles where it suggests I should run an a scheduled task to scrape for the modal dialog box but I've tried it without much luck.  If you can please give me some pointers on resolving this issue. 
    Thnx
    Sue.
    $ie.Document.getElementsByTagName("button") | ? { $_.innerText -eq 'UNLOCK User' } | Select-Object -first 1 | % { $_.Click() }
    Sue

  • Focus Problem -- Two Non Modal Dialogs

    Hi ,
    In my applet, when user does something which is not allowed, I display an error message box (JOptionPane dialog - modal).
    There is another dialog box (non modal) that user
    can open to view search results and put it aside the
    applet window to do some parallel work.
    Now when error message dialog appears, the search
    dialog box also pops up even if the user
    has put this behind the applet window (by clicking browser window or applet, the search dialog goes behind the window).
    Can you please let me know, how can I get rid
    of this search dialog (non-modal) popup. I mean
    search dialog should remain open but should not
    come infront (ie should not get focus) when modal
    error message dialog pops up.
    NOTE: I don't want to make search dialog
    a modal dialog.
    Thanx,
    [email protected]

    Thanks for the reply michael. I forgot to mention particularly during my post that i am facing this problem on Solaris system. Running the same application on windows is working fine. I can't make other non-modal dialogs visibility to false because they should be visible on the screen all the time throught out the application life cycle and making it visible/non-visible doesn't get sense in my application. Does anybody is facing the same problem with Solaris system? Plz help.
    Hitesh

  • How to remove the default icons from the toolbar of modal dialog box screen

    Hello Friends,
    Iam calling a screen from function module using CALL SCREEN statement.
    The screen is of type Modal Dialog Box. I created some input fields and buttons in the screen. When the screen is displayed, I can see the tool bar at the bottom along with the input fields and buttons in the screen.
    These icons are Continue(Enter), Check, Cancel. How can I supress this??
    I mean in my screeen I want only my input fields and buttons but not the default toolbar. How to do that?
    Regards,
    Raju

    Hi Raju,
    Try this...
    First try to capture the F-codes of ur button apppearing on the dialog box and then exclude it from the PF-status by passing it to itab.
    types: begin of tab_type,
            fcode like rsmpe-func,
           end of tab_type.
    data: tab type standard table of tab_type with
                   non-unique default key initial size 10,
          wa_tab type tab_type.
    clear tab.
    move 'DELE' to wa_tab-fcode.
    append wa_tab to tab.
    move 'PRIN' to wa_tab-fcode.
    append wa_tab to tab.
    set pf-status 'STA3' excluding tab.
    Cheers,
    Simha.
    Reward all the helpful answers..

  • ALV in modal dialog box

    Hi,
    I have an ALV on suppose screen 3000, I have created a button in the tool bar to call another ALV, but my question is, can we display ALV in modal dialog box screen(because the requirement is to display ALV as a popup)
    So when i changed the screen type to normal screen, my alv is coming,,but when i change the screen type to modal dialog box, then no ALV is being displayed in the output. Only blank screen is displayed.
    Can you please help me.
    Thanks.

    Hello
    The problem is that you have to take into account that the ALV in the popup (or modal dialogbox) is displayed on a different screen level:
    level 0 = main screen
    level 1 = 1st popup
    level 2 = 2nd popup
    We have up to 9 screen level available.
    The following sample report ZUS_SDN_ALV_IN_POPUP is a variant of my sample report ZUS_SDN_TWO_ALV_GRIDS.
    Depending on whether you mark P_POPUP or not the second ALV grid is additionally displayed on a popup.
    *& Report  ZUS_SDN_ALV_IN_POPUP
    *& Thread: ALV in modal dialog box
    *& https:||<a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="762642"></a>
    *& Screen '0100' contains no elements.
    *& ok_code -> assigned to GD_OKCODE
    *& Flow logic:
    *  PROCESS BEFORE OUTPUT.
    *    MODULE STATUS_0100.
    *  PROCESS AFTER INPUT.
    *    MODULE USER_COMMAND_0100.
    REPORT  zus_sdn_alv_in_popup.
    TYPE-POOLS: abap.
    DATA:
      gd_okcode        TYPE ui_func,
      gd_repid         TYPE syst-repid,
    " containers and ALV grids for main screen
      go_docking       TYPE REF TO cl_gui_docking_container,
      go_splitter      TYPE REF TO cl_gui_splitter_container,
      go_cell_top      TYPE REF TO cl_gui_container,
      go_cell_bottom   TYPE REF TO cl_gui_container,
      go_grid1         TYPE REF TO cl_gui_alv_grid,
      go_grid2         TYPE REF TO cl_gui_alv_grid,
    " container and ALV grid for popup
      go_docking3      TYPE REF TO cl_gui_docking_container,
      go_grid3         TYPE REF TO cl_gui_alv_grid,
      gs_layout        TYPE lvc_s_layo.
    DATA:
      gt_knb1          TYPE STANDARD TABLE OF knb1,
      gt_knvv          TYPE STANDARD TABLE OF knvv.
    PARAMETERS:
      p_popup AS CHECKBOX DEFAULT ' '.
    *       CLASS lcl_eventhandler DEFINITION
    CLASS lcl_eventhandler DEFINITION.
      PUBLIC SECTION.
        CLASS-METHODS:
          handle_double_click FOR EVENT double_click OF cl_gui_alv_grid
            IMPORTING
              e_row
              e_column
              es_row_no
              sender.
    ENDCLASS.                    "lcl_eventhandler DEFINITION
    *       CLASS lcl_eventhandler IMPLEMENTATION
    CLASS lcl_eventhandler IMPLEMENTATION.
      METHOD handle_double_click.
    *   define local data
        DATA:
          ls_knb1      TYPE knb1.
        CHECK ( sender = go_grid1 ).
        READ TABLE gt_knb1 INTO ls_knb1 INDEX e_row-index.
        CHECK ( ls_knb1-kunnr IS NOT INITIAL ).
        IF ( p_popup = abap_true ).
          CALL METHOD cl_gui_cfw=>set_new_ok_code
            EXPORTING
              new_code = 'POPUP'
    *        IMPORTING
    *          rc       =
        ELSE.
    *     Triggers PAI of the dynpro with the specified ok-code
    *  *    CALL METHOD cl_gui_cfw=>set_new_ok_code( 'DETAIL' ).  " not on 4.6c
          CALL METHOD cl_gui_cfw=>set_new_ok_code
            EXPORTING
              new_code = 'DETAIL'
    *        IMPORTING
    *          rc       =
        ENDIF.
      ENDMETHOD.                    "handle_double_click
    ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
    START-OF-SELECTION.
    " Select data
      SELECT        * FROM  knb1 INTO TABLE gt_knb1
             WHERE  bukrs  = '1000'.
      PERFORM init_controls.
    * Display data
      gs_layout-grid_title = 'Customers'.
      CALL METHOD go_grid1->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNB1'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_knb1
        EXCEPTIONS
          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.
      gs_layout-grid_title = 'Customers Details (Sales Areas)'.
      CALL METHOD go_grid2->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNVV'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_knvv  " empty !!!
        EXCEPTIONS
          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.
      gs_layout-grid_title = 'Customers Details (Sales Areas)'.
      CALL METHOD go_grid3->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNVV'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_knvv  " empty !!!
        EXCEPTIONS
          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.
    * Link the docking container to the target dynpro
      gd_repid = syst-repid.
      CALL METHOD go_docking->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0100'
    *      CONTAINER                   =
        EXCEPTIONS
          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.
    * Link the docking container to the popup
      gd_repid = syst-repid.
      CALL METHOD go_docking3->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0200'
    *      CONTAINER                   =
        EXCEPTIONS
          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.
    * NOTE: dynpro does not contain any elements
      CALL SCREEN '0100'.
    * Flow logic of dynpro (does not contain any dynpro elements):
    *PROCESS BEFORE OUTPUT.
    *  MODULE STATUS_0100.
    *PROCESS AFTER INPUT.
    *  MODULE USER_COMMAND_0100.
    END-OF-SELECTION.
    *&      Form  INIT_CONTROLS
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM init_controls .
    * Create docking container
      CREATE OBJECT go_docking
        EXPORTING
          parent = cl_gui_container=>screen0  " main screen -> level 0 !!!
          ratio  = 90
        EXCEPTIONS
          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 splitter container
      CREATE OBJECT go_splitter
        EXPORTING
          parent            = go_docking
          rows              = 2
          columns           = 1
    *      NO_AUTODEF_PROGID_DYNNR =
    *      NAME              =
        EXCEPTIONS
          cntl_error        = 1
          cntl_system_error = 2
          OTHERS            = 3.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Get cell container
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = 1
          column    = 1
        RECEIVING
          container = go_cell_top.
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = 2
          column    = 1
        RECEIVING
          container = go_cell_bottom.
    * Create ALV grids
      CREATE OBJECT go_grid1
        EXPORTING
          i_parent = go_cell_top
        EXCEPTIONS
          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.
    * Set event handler
      SET HANDLER: lcl_eventhandler=>handle_double_click FOR go_grid1.
      CREATE OBJECT go_grid2
        EXPORTING
          i_parent = go_cell_bottom
        EXCEPTIONS
          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.
      " Create container and grid for popup.
    * Create docking container
      CREATE OBJECT go_docking3
        EXPORTING
          parent = cl_gui_container=>screen1 " !!! popup !!!
          ratio  = 90
        EXCEPTIONS
          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.
      " NOTE: Starting from a main dynpro (screen level 0) the first popup
      "       (or modal dialogbox) is on level 1 !!!
      " Using cl_gui_container=>screen0 fails to display ALV grid.
      CREATE OBJECT go_grid3
        EXPORTING
          i_parent = go_docking3
        EXCEPTIONS
          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.
    ENDFORM.                    " INIT_CONTROLS
    *&      Module  STATUS_0100  OUTPUT
    *       text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'STATUS_0100'.  " contains push button "DETAIL"
    *  SET TITLEBAR 'xxx'.
    * Refresh display of detail ALV list
      CALL METHOD go_grid2->refresh_table_display
    *    EXPORTING
    *      IS_STABLE      =
    *      I_SOFT_REFRESH =
        EXCEPTIONS
          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.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    *       text
    MODULE user_command_0100 INPUT.
      CASE syst-dynnr.
        WHEN '0100'.
          CASE gd_okcode.
            WHEN 'BACK' OR
                 'END'  OR
                 'CANC'.
              SET SCREEN 0. LEAVE SCREEN.
    *   User has pushed button "Display Details"
            WHEN 'DETAIL'.
              PERFORM entry_show_details.
            WHEN 'POPUP'.
              PERFORM entry_show_details.
              go_grid3->refresh_table_display( ). " required
              CALL SCREEN '0200' STARTING AT 5 5
                                 ENDING   AT 150 30.
            WHEN OTHERS.
          ENDCASE.
        WHEN '0200'.
          set screen 100. leave screen.
      ENDCASE.
      CLEAR: gd_okcode.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    *&      Form  ENTRY_SHOW_DETAILS
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM entry_show_details .
    * define local data
      DATA:
        ld_row      TYPE i,
        ls_knb1     TYPE knb1.
      CALL METHOD go_grid1->get_current_cell
        IMPORTING
          e_row = ld_row.
      READ TABLE gt_knb1 INTO ls_knb1 INDEX ld_row.
      CHECK ( syst-subrc = 0 ).
      SELECT        * FROM  knvv INTO TABLE gt_knvv
             WHERE  kunnr  = ls_knb1-kunnr.
    ENDFORM.                    " ENTRY_SHOW_DETAILS
    Regards
      Uwe

  • Howto create non-modal dialogs using ADF Faces

    I would like to use Dialogs in a non-modal manner.
    Trying to use
    <af:commandLink useWindow="true" action="dialog:infoPopup" blocking="false">
    <af:setActionListener from="#{row.xyId}" to="#{infoPopup.currentId}" />
    </af:commandLink>
    doesn't work as expected. I'll get the dialog, but I can't use the page behind it.
    Alternatively I tried to show the page using Javascript opening the pageInfo.faces, but here I have an order problem. The onClick event is processed first and the #{infoPopup.currentId} will be populated after rendering the JSF page. But I want to show infos depending on the xyId.
    Is there any other way to open windows/dialogs?
    Thanks in advance
    Stephan

    The "blocking" attribute basically just blocks you from clicking the commandLink or commandButton twice (or more) before the first click has been processed by the server and a response has been received.
    It is a very good util for avoiding those unwanted IndexOutOfBoundsExcepions when a user hits many buttons thus sending multiple requests to the server.
    By the way, I'd like to see the answer to the non-modal dialog window, because we have a need for them, too.
    Kind regards,
    dj

  • Unable to close Modal dialog box

    Hello Friends,
    I am displaying a list in a Modal Dialog box. When I try to close the Modal dialog box. It is not getting closed.I have defined a gui status for this modal dialog box. PBO and PAI Coding is given below .
    module STATUS_0300 output.
      SET PF-STATUS 'STATUS_300'.
    SUPPRESS DIALOG.
      LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0 .
      IF p_week IS NOT INITIAL.
        WRITE : text-009 COLOR 1.
      ENDIF.
      IF p_month IS NOT INITIAL.
        WRITE : text-010 COLOR 1.
      ENDIF.
      LOOP AT g_t_wkmon_error INTO g_s_wkmon_error.
        WRITE :/ g_s_wkmon_error-matnr,
                 g_s_wkmon_error-period,
                 g_s_wkmon_error-quantity.
      ENDLOOP.
    LEAVE SCREEN.
    endmodule.  
    module USER_COMMAND_0300 input.
    CASE ok_code.
      WHEN 'OK'.
       LEAVE PROGRAM.
    ENDCASE.
    endmodule. 
    Thanks in Advance.
    Hari

    Hi,
    Check the below thread
    Re: Unable to close modal dialog box
    " Make sure you select the Radio Button DIalog BOX Typ while creating the Status in PBO
    You can use SET SCREEN 0 In the above Thread
    MODULE user_command_0100 INPUT.
      CASE ok.
        when 'CANCEL'. " You Standard GUI options shown in The GUI Screen
          SET SCREEN 0.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    module STATUS_0100 output.
    SET PF-STATUS 'ABC'. " This is of type Dailog Box type
    *  SET TITLEBAR 'xxx'.
    endmodule.                 " STATUS_0100  OUTPUT
    Hope this would resolve your Issue.
    Cheerz
    Ram
    Edited by: Ramchander Krishnamraju on Apr 16, 2010 1:16 PM

  • Is it possible to call a subscreen/modal dialog box from the global class

    Hi,
    Is it possible to call a subscreen or modal dialog box from the global class ..
    or is there any option to display a pop screen or subscreen in order to get the values from user which as to be implemented
    in the global class..
    thanks and regards,
    Poornima.

    Hi Poornima,
    you should follow Uwe's suggestion. The only alternative I can imagine is dynamic document in a dialog container. But I don't know any standardized classes to make use with minimum effort. Have a look at report DD_ADD_FORM_INPUT. Here they put the input field in a container control in a screen; you can put the container control on a dialog container (CL_GUI_DIALOGBOX_CONTAINER).
    We will not get rid of any screen for the time being, but if your application is started from any screen, the DIALOGBOX_CONTAINER can start from there.
    Regards,
    Clemens

  • SBO running in TSRemoteApp crashes when clicking on Modal dialog box

    We have a customer who has installed SAP Business One 8.81.316 PL08 on Windows Server 2008 R2.  The application is accessed by users using RemoteApp.  The application generally runs well, however, when a user is presented with a Modal dialog box (i.e. Do you really want to delete Y/N) and clicks on the dialog box, the foreground RemoteApp session crashes.  If the user then reconnects to the back end session, the application is exactly as it should be, with the dialog box still displayed.
    When connecting by a normal RDP type session, the problem isn't evident.
    Has anyone experienced this behaviour? 

    I realize this is a very old topic, but I've run into the same problem.
    I can't get PrimeFaces modal dialog to work in Internet Explorer 7 using JSF2/facelets/PrimeFaces 2.0.2.
    So I am looking for alternatives, but have not found anything so far.
    Any hints?
    Edited by: burferd on Jun 21, 2010 7:56 PM

  • How do you use the Multiple Item Information dialog box ???

    How do you use the Multiple Item Information dialog box ???
    Where are the instructions on how the information in the Multiple Item Information dialog box equates to ...
    1. The way iTunes sorts tracks and albums
    2. The reason to select a leading check box
    3. Why there are Option selections (Yes /No) and leading check boxes.
    4. Why some changes remain in the track info, but do not "take effect" in iTunes (Part of a compilation is an example)
    Looked in Help, Support, went to the local Genius bar for an hour, even arrainged a call from apple support ...
    Thanks

    As Christopher says, it's a compilation. Different tracks are by different artists.
    Setting the *Album Artist* field to *Various Artists* and setting *Part of a compilation* to Yes should be all that is required. Depending on your *Group compilations when browsing* setting ( I recommend On ) either should suffice but I suggest doing both.
    Based on your commentary, I selected all the "O Brother" tracks, and checked the boxes for everything line that was blank in the Info and the Sort panes. Only exceptions were the album name and the disc number 1 of 1 and the artwork. I blanked and checked anything else.
    That's not what I meant. When you select multiple tracks, only those values which +are already common+ to all tracks are displayed. Typically these will include Artist, though not with compilation albums, Album Artist, Album, No. of Tracks, Genre plus various sort fields. A blank value may indicate that different tracks have different values or it may be that the value is blank for all tracks. For the drop down values on the Options tab the value shown may not reflect the information in every tag. If values you expect to be common, such as Album Artist or the Album title are not displayed you can simply type these in and click OK. This will often be enough to group the album.
    If you place a checkmark against the blank boxes and apply changes then you will clear those fields so you should only do this if that is the effect you want. Putting a checkmark next to an empty (representing different values) *Track No.* box, for example, will just clear the all the track numbers which is very rarely useful.
    Adding then removing extra text is for a specific problem where despite all common values being identical across the tracks of the album iTunes seems to "remember" that it should see two albums. A typical example would be when an album originally listed as *Album CD1* & *Album CD2* is given disc numbers X of Y and then has the Album name changed to Album. I've seen iTunes merge all but one track into the new album, but insist on listing one remaining track separately, despite both albums having the same title. In this case I've found overtyping the album title again has no effect whereas changing it to AlbumX and then back to Album does what I was trying to achieve in the first place.
    Don't forget that even properly organsied albums may still break up if you don't chose an album-friendly view. Sorting on the track name or track number columns can be useful in some circumstances but in general I revert to Album by Artist when browsing through my library.
    tt2

  • Calling Selection Screen in Modal dialog box

    Hi Experts.
    I have created screen 9000 having user interface and in tool bar there is create button in the screen 9000
    The create button 9001 will call another screen with different I/O fields (9001 is Modal dialog screen).
    In the 9001 there is push button for which the selection screen is called 9002.
    I have declared 9002 as subscreen and called the screen 9002 in user command.
    In the Screen 9001 when user clicks the push button i need to get pop up screen where the user select some data.
    How i need to do ?
    I am getting error can't call subscreen in modal dialog box.
    Thanks,
    ERPSAP

    HI,
    HOpe this will help you
    How to call table control in subscreen in module pool program
    http://sap.ittoolbox.com/groups/technical-functional/sap-dev/reg-tab-strip-control-module-pool-abap-444944
    http://12go.com/sap/search?query=title%3A(calling%20subscreens%20in%20module%20pool)
    Regards,
    Pravin

  • Standard 'X' in a modal dialog box not working

    Hi,
    I have created a module pool and calling screen from main screen using Call screen.... Starting... ending... statement.
    It is a modal dialog box screen. As a standard a [X] appears on top right corner. But when I click it doesn't work. it does not even fire PBO. How can I make it work?

    Hi,
    Set next screen as 0, not the screen itself. Then you are able to close it this way.
    Regards
    Marcin
    I was wrong, this will only close the modal box each time after the dialog step is completed. To activate this magic 'X' (allow closing the window with ALT+F4) in PBO set status (type dialog box ) and activate CANCEL and CONTINUE buttons. Now when you try closing the window either by CANCEL button or using X, sy-ucomm (ok_code of the screen) will store CANCEL function code. This way you can simply say LEAVE SCREEN . That works fine, I checked.
    Regards
    Marcin
    Edited by: Marcin Pciak on Mar 17, 2009 11:16 PM

  • Screen sequence processing when using modal dialog box

    I have been struggling with a dialog program which I have written.  I have a screen which has 2 radiobuttons and a check box (screen 100).  If the checkbox is marked, a modal dialog screen pops up (screen  150).  If I complete both input fields on  screen 150, I can go through to screen 200, then back out of screen 200 to screen 100, and then I can back out 100 to screen 0.
    The problem I have is the validation I have put in screen 150 if one or both input fields have no values or if I want to exit screen 150.  If I exit screen 150, in order to get back to screen 100 in the main screen I need to do CALL SCREEN 100 as if I use SET SCREEN 100, 100 then appears in my modal dialog box screen.
    If I try to back out of screen 100 to screen 0, the program then brings up screen 150 in the PAI part of the module and then go to screen 0 when I close screen 150 even though I have coded SET SCREEN 0. LEAVE SCREEN. in the user command module of screen 100.  Here is my code:
    <u><b>screen 100</b></u>
    PROCESS BEFORE OUTPUT.
      MODULE status_0100.
    PROCESS AFTER INPUT.
      MODULE user_command_0100.
    <b>
    <u>Modules for 100</u></b>
    *&      Module  STATUS_0100  OUTPUT
    *       text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'ZL_PWB_GR1'.
      SET TITLEBAR  'ZL_PWB_GR1'.
      CLEAR: w_hse_stock, w_new_product, wa_sto, w_reverse,
             mara-matnr,  mkpf-mblnr.
      PERFORM release_lock.
      REFRESH CONTROL 'TC_GR' FROM SCREEN 0200.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    *       text
    MODULE user_command_0100 INPUT .
      CASE ok_code.
        WHEN 'ENTER'.
          IF w_reverse = space.
            CALL SCREEN 0200.
          ELSE.
            CALL SCREEN 0150 STARTING AT 30 2
                             ENDING AT   75 5.
          ENDIF.
        WHEN 'BACK' OR 'EXIT' OR 'CANC'.
          w_pai = c_yes.
          SET SCREEN 0.
          LEAVE SCREEN.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    <u><b>screen 150</b></u>
    PROCESS BEFORE OUTPUT.
      MODULE status_0150.
    PROCESS AFTER INPUT.
      MODULE exit_command_0150 AT EXIT-COMMAND.
      FIELD  mara-matnr MODULE check_matnr.
      FIELD  mkpf-mblnr MODULE check_art_doc.
    <u><b>Modules for 150</b></u>
      MODULE user_command_0150.
    *&      Module  STATUS_0150  OUTPUT
    *       text
    MODULE status_0150 OUTPUT.
      SET PF-STATUS 'GR_REV'.
      SET TITLEBAR 'GR_REV'.
    ENDMODULE.                 " STATUS_0150  OUTPUT
    *&      Module  exit_COMMAND_0150  INPUT
    *       text
    MODULE exit_command_0150 INPUT.
      IF sy-ucomm = 'EXIT'.
        CALL SCREEN 100.
      ENDIF.
    ENDMODULE.                 " exit_COMMAND_0150  INPUT
    *&      Module  check_matnr  INPUT
    *  Check if issues has been filled and if issue is a valid article no.
    MODULE check_matnr INPUT.
      DATA: l_matnr TYPE matnr.
      IF mara-matnr IS INITIAL.
        MESSAGE i010(ad) WITH 'Issue no. required'.
        EXIT.
      ELSE.
        SELECT SINGLE matnr FROM mara INTO l_matnr
         WHERE matnr = mara-matnr.
        IF sy-subrc NE 0.
          CLEAR l_matnr.
          MESSAGE i010(ad) WITH 'Issue does not exist'.
        ENDIF.
      ENDIF.
    ENDMODULE.                 " check_matnr  INPUT
    *&      Module  check_art_doc  INPUT
    *       text
    MODULE check_art_doc INPUT.
      IF mkpf-mblnr IS INITIAL.
        MESSAGE i010(ad) WITH 'Article document no. required'.
        EXIT.
      ELSE.
        PERFORM get_art_doc USING mara-matnr
                                  mkpf-mblnr.
        IF sy-subrc NE 0.
          MESSAGE i010(ad) WITH 'No article document exists for this issue'.
        ENDIF.
      ENDIF.
    ENDMODULE.                 " check_art_doc  INPUT
    *&      Module  USER_COMMAND_0150  INPUT
    *       text
    MODULE user_command_0150 INPUT.
      CASE sy-ucomm.
        WHEN 'ENTE'.
          IF mara-matnr NE space AND mkpf-mblnr NE space.
            CALL SCREEN 200.
          ELSE.
    *        MESSAGE i010(ad) WITH 'Please fill in both fields'.
            SET SCREEN 150.
          ENDIF.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0150  INPUT
    Any suggestions or pointers would be greatly appreciated as I am going round in circles.
    Thanks
    Larissa

    Have got around this by removing the references to SET SCREEN 150.  This way, I can get around the screen sequencing.  It just means that I cannot keep my screen 150 in view if a validation message occurs but for now it will do for what I need.
    Thank you for your help anyway.
    Larissa

Maybe you are looking for

  • Mouse won't scroll for one User but works for another

    I recently updated to a new Imac and restored the computer from time machine from our old IMac which didn't have mountain lion update.  All works fine except when logged onto our Kids account the mouse wont scroll pages by sliding finger on the mouse

  • Widgets in Desktop?

    Simple Question: Can I put my widgets in the desktop? ~Christoph

  • How to corret an execution plan that shows wrong number of rows?

    Using Oracle 10gR2 RAC (10.2.0.3) on SUSE Linux 9 (x86_64). I have a partition table that has 5 million rows (5,597,831). However an execution plan against the table show that the table has 10 million rows. Execution plan: SELECT STATEMENT ALL_ROWS C

  • What is he order of installion for the labview 7.1 cd's

    I aqm trying to install labview 7.1, everytime I try to install one thing, it tells me I need to install something else to intall all the features of that item. There must be some sequence you are supposed to follow, do you install the one labeled La

  • Why on earth is there no free print ability?

    What gives?  If the only solution from the company is to buy someone ELSES print app ... seems to me they left out something.  Sort of like leaving off the mirrors in your car.  Why is there no real outrage here?  Doesn't anyone else WANT to use this