Call a dialog box by a function key

hi,
     i am having a alv report with alv rows having colors depending on certain condition.i want a color legend (a dialog box that has description of the color function) on pressing f6 function key.
any comments.

Hi.
Declare a GUI status for the ALV.
In the GUI status, define an OK code for the F6 key.
In the form for processing ALV user commands, if it is this OK code, display your dialog box.
There are function modules for dialog boxes, but perhaps the neatest here would be another ALV.
John

Similar Messages

  • What are the advantages of utilizing a dynamic VI compared to utilizing the VI Call Configuration Dialog Box Reload for each call option?

    Is it more efficient to use a dynamic VI or utilize the VI Call Configuration Dialog Box which apparently can perform the same function? I realize that there are restrictions on using the VI Call Configuration Dialog Box, however, if my scenario doesn't concern the restrictions, why would I want to go thru the trouble of creating a dynamic VI when I could simply click on the VI of interest and configure from a menu? Are there performance advantages? Thanks in advance!

    Generally, I wouldn't recommend playing with the call setup dialog at all (for those who don't know it, you can get to it by right clicking a subVI in the BD). By default, VIs are configured to load with callers and that's the correct options for almost all static VIs. The Open VI Reference primitive has multiple advantages:
    It allows you to select different VIs dynamically.
    It allows you to spawn multiple copies of reentrant VIs.
    It allows you to perform asynch runs (although I think that this is something that should actually be available through the call setup dialog).
    It allows you to open references to VIs in other application instances.
    In the rare cases where you do want the same functionality that the call setup dialog gives you, it doesn't hide it.
    Try to take over the world!

  • Dialog Box does not function when called a second time

    I have created a dialog box that only seems to work once in a larger application. The box is designed to be a MatLab code debugger. My idea was to allow a user to interactively create/debug Matlab code from LabView using ActiveX automation. Anyway, I have created a test vi that uses this dialog box twice. The first time it is called it functions as expected, but the second time nothing on the front panel (of the dialog box) responds and I cannot close the window or interrupt the vi. I am using LabVIEW 7.0 on Windows 98. Please see the attached vi's. MatlabDebugger.vi is the dialog that's causing the problem. Matlabx2.vi is the sub vi that handles the ActiveX automation. Debuggertest.vi is the test v
    i in which the dialog will not word a second time.
    Thanks in advance for any help or suggestions.
    Attachments:
    Debuggertest.vi ‏51 KB
    MatlabDebugger.vi ‏303 KB
    Matlabx2.vi ‏361 KB

    The problem is caused by the nested event structures; you have an event structure inside an event structure, acting on the same controls. When the main one reacts to the cancel the other one get's stuck...so on the next call the main event structure just halts due to the stuck event structure inside it. It's not obvious why this is a fault, you may be able to spot it now that you're on the track though.
    MTO

  • How can I display the failure caption with click box when using function keys to navigate a sim?

    I am using the keyboard function keys to navigate a simulation using Click Boxes. For instance, F7 advances the simulation to the next screen, but if the learner selects F5, a failure caption displays. I have tried deleting and re-entering the click box, placing the click box at the top of the timeline levels, starting the click box at 0 and 0.5, making the click box visible and invisible, and make the click box the entire size of the screen.

    Well, I guess that's that. Thanks for replying, I do appreciate it or else I would have been trying for days, wasting all sorts of time.
    Until we meet again,
    James

  • Can't close levels dialog box by pressing ENTER key, how to fix?

    Using Windows 8.1.
    I could close the levels dialog box (CTR-L) by hitting ENTER key in CS6. Doesn't work like that in CC and I can't find a preference to change the behavior.
    Thanks in advance.

    You realise that Enter works on whatever is the active button?  That defaults to the OK button when you open Levels, and stays there if you just adjust the sliders, but will move to whatever button you click on i.e. Auto.   If you really want to use the keyboard, then hitting Shift Tab a couple of time will move you back from Auto to OK and you can then hit enter to close the dialog box.

  • How to call a dialog box from a frame

    I have an application with menu driven Frame. on clicking one of the options i have to open a dialog box. how can this done?
    any help is appreciated.
    thanks
    partha

    Just create the dialog resource in the resource editor, then create a class for it in class wizard. Next, include the header for that class in your view class, then install a menu event handler in the view class for the menu item you want to launch the dialog from. In that event handler create a object of the dialog class and call .DoModal() something like:
    CMyDialog dlg;
    dlg.DoModal();
    That's pretty much it.
    Best Regards,
    Chris Matthews
    National Instruments

  • How can I create a new UDL w/o calling a dialog box, or going through Windows?

    I'm using Labview 6.1 and the Database Connectivity Toolset. I know the conventional ways of creating a UDL, but with the SQL toolkit there was a vi on the Knowledgebase site that created a DSN seamlessly, with no dialog boxes at all. Is there such a thing to create a new UDL?

    Depending on your operating system, things may be slightly different, but on Win 2k, use the administrative tools->Data Sources Administrator to create some sample DSNs that you can look at. You want to create a 'file DSN,' as 'User DSN's and 'System DSN's appear to be stored elsewhere. (Maybe in the registry)
    I'm attaching an example DSN that I have been using as well.
    Best of Luck to you,
    Alex
    Attachments:
    electrode.dsn ‏1 KB

  • Calling windows dialog box in web based Forms6i application

    Hi !!
    I have develop a form in form6i. On pressing a button(on the form) windows OPEN FILE dialog box appears,from this user choose the required file.
    I m using the GET_FILE_NAME built in for this purpose and it is working in client server mod.
    The problem is it does not work when I post the form on web or run it in web.

    This will not work on the web. If you want to present the use with a file dialog box this will have to be done using a java bean.
    Regards
    Grant Ronald.

  • Step that calls a dialog box (modal screen) does not work

    Hi,
    I have a workflow step that has a method which calls a function module that calls a screen (text editor screen).
    When I execute the workflow in test mode (SWUS), the screen shows up.
    But when I execute the work item from the Business Workplace, the screen does not show up.
    Your help is greatly appreciated.
    Thank you.
    Giscard

    Hi,
    Check the Agent assignment for that Task. And Make that Task as a General Task.
    Regards,
    Surjith

  • Display document data in dialog box

    I am using a folder level script to do the following:
    Get a specific XMP field value from an open PDF file:
    this.info.InDesignFileName
    Define a dialog box
    Create a menu item that calls the dialog box
    But for the life of me, I cannot get the dialog creation function to populate the XMP value into a static text item.
    The function below is modified from the example right out of the Acrobat Javascript API Reference.
    var inDesignNameDialog = {
    initialize: function (dialog) {
    // store InDesignFileName XMP
    //var indfn = this.info.InDesignFileName
    // Create a static text containing the current date.
    /*var todayDate = dialog.store()["date"];
    todayDate = "Date: " + util.printd("mmmm dd, yyyy", new Date());
    dialog.load({ "date": todayDate });
    var todayDate = dialog.store()["indfn"];
    currFN = "Date: " + this.info.InDesignFileName;
    dialog.load({ "indfn": currFN });
    commit:function (dialog) { // called when OK pressed
    var results = dialog.store();
    // Now do something with the data collected, for example,
    console.println("Your name is " + results["fnam"]
    + " " + results["lnam"] );
    description:
    name: "Personal Data", // Dialog box title
    align_children: "align_left",
    width: 350,
    height: 200,
    elements:
    type: "cluster",
    name: "Your Name",
    align_children: "align_left",
    elements:
    type: "view",
    align_children: "align_row",
    elements:
    type: "static_text",
    name: "First Name: "
    item_id: "fnam",
    type: "edit_text",
    alignment: "align_fill",
    width: 300,
    height: 20
    type: "view",
    align_children: "align_row",
    elements:
    type: "static_text",
    name: "Last Name: "
    item_id: "lnam",
    type: "edit_text",
    alignment: "align_fill",
    width: 300,
    height: 20
    type: "static_text",
    name: "InDesign File Name: ",
    char_width: 50,
    item_id: "indfn"
    alignment: "align_right",
    type: "ok_cancel",
    ok_name: "Ok",
    cancel_name: "Cancel"

    By gosh, you are right. Thanks for the tip.
    However, it still does not seem to be working:
    The static text field is just empty.
    The debugger shows error:
    parentDoc is not defined
    11:Menu:ExecReferenceError: parentDoc is not defined([object ADMDialog])@Menu:Exec:11
    execDialog([object Object])@:0
    @Menu:Exec:1
    Your name is 
    Code as it stands right now:
    var inDesignNameDialog = {
    initialize: function (dialog) {
    var currFN = dialog.store()["idfn"];
    currFN = parentDoc.info.InDesignFileName;
    dialog.load({ "idfn": currFN });
    commit:function (dialog) { // called when OK pressed
    var results = dialog.store();
    // Now do something with the data collected, for example,
    console.println("Your name is " + results["fnam"]
    + " " + results["lnam"] );
    description:
    name: "Personal Data", // Dialog box title
    align_children: "align_left",
    width: 350,
    height: 200,
    elements:
    type: "cluster",
    name: "Your Name",
    align_children: "align_left",
    elements:
    type: "view",
    align_children: "align_row",
    elements:
    type: "static_text",
    name: "First Name: "
    item_id: "fnam",
    type: "edit_text",
    alignment: "align_fill",
    width: 300,
    height: 20
    type: "view",
    align_children: "align_row",
    elements:
    type: "static_text",
    name: "Last Name: "
    item_id: "lnam",
    type: "edit_text",
    alignment: "align_fill",
    width: 300,
    height: 20
    type: "static_text",
    name: "InDesign File Name: ",
    char_width: 50,
    item_id: "idfn",
    alignment: "align_right",
    type: "ok_cancel",
    ok_name: "Ok",
    cancel_name: "Cancel"

  • Dialog Box simulation without interrupting program flow

    I'm developing data acquisition/control software and need to give the end
    user flexibility to change the file to which the acquired data is being
    saved during operations. In the past, users have been confused with a
    simple string control that specifies the data file path, so I would prefer
    to move to the popup/dialog box standard to windows. Unfortunately, calling
    a dialog box results in the stoppage of program flow for the caller until
    the dialog box is closed (even though there may be no apparent data flow
    from the popup VI.) and stopping the program flow is not an option for this
    control system (the computer is controlling pressure, temperature, flow
    rates, etc of a very expensive and sensitive bit of hardware, so halting the
    control function for an unknown length of time is unacceptable).
    I am looking for the best way to accomplish this under LabVIEW 6i.
    Using a VI class reference through VI Server, I can essentially detach the
    popup window from the base program execution, spawning a separate
    application and passing the relevant parameters through judicious use of
    global variables. If I call the subroutine via VI server with "Wait until
    done" attribute set to false, the appropriate VI appears, functions
    correctly, and terminates as expected. Unfortunately, it remains visible on
    the screen, an inactive application. I have the VI Properties -> Window
    Appearance -> Customize -> Show Front Panel When Called and the Close
    Afterwards if Originally Closed checkboxes checked on this popup VI. It
    seems that calls through VI Server trigger the "Originally Open" flag, so
    the window does not close as I had expected.
    The way I have found to get around this problem is to use VI Server to call
    an intermediate subroutine whose front panel is not displayed and whose sole
    purpose it to call the subroutine that calls the dialog box. This does what
    I wanted, essentially. When the user wants to change directories, they
    press a button that triggers a call to VI Server to open a separate
    application. This application's front panel is never displayed and only
    calls a sub-VI that performs all the actual work and ends when it is
    completed. As this sub-VI terminates, all visible traces of the subroutines
    disappear and I'm left with just the primary program executing, continuing
    to take and send control signals through this whole process.
    This seems a rather cumbersome way to get a custom dialog box on the screen
    without stopping the program flow of the caller, however. Is there a more
    efficient way to accomplish this?
    Wade C. Eckhoff
    [email protected]

    Wouldn't it be easier to use two parallel independent while loops in the
    main vi, with one taking care of acquisition and the other of user
    interaction.
    When the UI loop is temporarily 'halted' because of the dialogue box poping
    up, the acquiring loop continues without delay.
    Regards
    Harrie Boonen
    www.novonordisk.com
    "Default User" wrote in message
    news:[email protected]...
    > I'm developing data acquisition/control software and need to give the end
    > user flexibility to change the file to which the acquired data is being
    > saved during operations. In the past, users have been confused with a
    > simple string control that specifies the data file path, so I would prefer
    > to move to the popup/dialog box standard to windows. Unfortunately,
    calling
    > a dialog box results in the stoppage of program flow for the caller until
    > the dialog box is closed (even though there may be no apparent data flow
    > from the popup VI.) and stopping the program flow is not an option for
    this
    > control system (the computer is controlling pressure, temperature, flow
    > rates, etc of a very expensive and sensitive bit of hardware, so halting
    the
    > control function for an unknown length of time is unacceptable).
    >
    > I am looking for the best way to accomplish this under LabVIEW 6i.
    >
    > Using a VI class reference through VI Server, I can essentially detach the
    > popup window from the base program execution, spawning a separate
    > application and passing the relevant parameters through judicious use of
    > global variables. If I call the subroutine via VI server with "Wait until
    > done" attribute set to false, the appropriate VI appears, functions
    > correctly, and terminates as expected. Unfortunately, it remains visible
    on
    > the screen, an inactive application. I have the VI Properties -> Window
    > Appearance -> Customize -> Show Front Panel When Called and the Close
    > Afterwards if Originally Closed checkboxes checked on this popup VI. It
    > seems that calls through VI Server trigger the "Originally Open" flag, so
    > the window does not close as I had expected.
    >
    > The way I have found to get around this problem is to use VI Server to
    call
    > an intermediate subroutine whose front panel is not displayed and whose
    sole
    > purpose it to call the subroutine that calls the dialog box. This does
    what
    > I wanted, essentially. When the user wants to change directories, they
    > press a button that triggers a call to VI Server to open a separate
    > application. This application's front panel is never displayed and only
    > calls a sub-VI that performs all the actual work and ends when it is
    > completed. As this sub-VI terminates, all visible traces of the
    subroutines
    > disappear and I'm left with just the primary program executing, continuing
    > to take and send control signals through this whole process.
    >
    > This seems a rather cumbersome way to get a custom dialog box on the
    screen
    > without stopping the program flow of the caller, however. Is there a more
    > efficient way to accomplish this?
    >
    >
    > Wade C. Eckhoff
    > [email protected]
    >
    >
    >

  • How to leave the current dialog box screen?

    Hi Experts,
    Now I met a problem when I use statement LEAVE SCREEN for closing current dialog box screen. The scenario is like this:
    There is a screen '0010' under function group A, on this screen, there are 4 tabs, i created a custom control element on tab 4. with this custom control I embeded a subscreen 0910 which is defined under function group B not A, in the PAI of subscreen 0910, i called another dialog box screen 0920 which is defined under function group B also. statement CALL SCREEN '0920' is used for this and it works fine.              
                    But now when i click on the X (cancel) button on the dialog box, it is not closed but still there. So i use statement 'LEAVE SCREEN TO 0910' for closing the dialog box, but finally, not only the dialog box screen is closed but the screens '0910', '0010' are also closed.
    I think the problem is because that screen '0010' and  '0910' , '0920' are not under same function group, but I don't know the solution for closing the dialog box only.
    Lynn Liu

    HI,
    Debug the program after you press the CANCEL button , you will get where the conrol is flowing , And instead of using
    Leave to screen '910'          use               Leave to screen 0.
    Regards,
    Madhukar Shetty

  • Remapping function keys the way users need them to

    Expose was a feature that I used seamlessly when going between apps on a MacBook. Ever since I got a MacBook Pro it's been frustrating using Expose and Spaces ever since.
    1. I never did use the hot corners. Way too many inadvertent calls, especially if you use all three. Plus, using the function keys are a lot faster.
    2. OK, so we finally don't need to use two hands for right-clicking, but why do we now need it for Expose and Spaces? When going between apps, my finger drifted easily and rapidly to F8, F9 and F10, but now I have to use two hands? This is especially annoying when you're just in review mode and using only one hand, on the phone, lounging, etc.
    3. I know I can reverse the function keys, but I'd like to control volume and screen display with one hand as well.
    Feature request: Rather than have a universal one-check-box switch between function keys and special features printed on the keys, I would absolutely be a lot more efficient and quicker in my workflow if I was simple allowed to choose whether I wanted each individual function key to be the special feature or a standard function. In other words, I'd like to use one hand to control volume, screen display, Spaces, and Expose. The backlit display and desktop viewer switch features are seldom if ever used for me - kind of a waste of efficiency.
    DoubleCommand, previously suggested, doesn't do this. Does anything?

    Thank you, I already did, but that's not the point of this post. The feature request is a small part of the message to explain what I'm looking for, either as a script or third party app or something I'm overlooking, or if I am indeed completely out of luck and that my only option was to have submitted a feature request.
    Message was edited by: Tux Kapono

  • Accessing dialog boxes in DW CS6

    My Dreamweaver CS6 software does not automatically bring up certain dialog boxes when their functions are invoked, specifically the Hyperlink dialog box and the Select Image Source dialog box.  There are obviously ways to do these functions without the dialog boxes, but I would like to know why they don't automatically pop up when I follow the instructions laid out in David McFarland's "The Missing Maual" book or various online tutuorials on Youtube.com and elsewhere.
      I am wondering if this could possibly be due to the fact that I purchased and downloaded the software from an online retailer called www.newoemsoftware.com at a greatly discounted price.  I was given a serial number and can register the software, so I would think that nothing is suspect about my software.

    Hi robtompk,
    It is highly unlikely that your problems are because of purchasing a discounted version of the software. Just to be sure, can you try closing other applications open on your computer, and try opening the dialog boxes in DW?
    Also, what is the build number that you have? Use Help > About to get this information.
    Thanks,
    Preran

  • Call Accept dialog pop up in Chat application

    Hello,
    I have made an Audio Video chat application in AS3 and using FMS as my server.I want to make the functionality of a call accept dialog box which pops up when one client wants to call another .Giving 2nd client the control to accept call or not like is done in Skype and all.Can anyone explain how will thisbe done using AS3.
    Thanx in advance..

    That would make for a quite a long tutorial, but to give you an idea of some sorts:
    1. Keep track of each user that connects so that you can contact them directly
    2. Notify the server side from the sending client side that they want to contact somebody, passing in the receiver's unique ID (that you create)
    3. Server side figures out which user that is and send them a notification
    4. Keep the state of the request on the server and client sides so that you can control how many requests they get etc
    5. Respond by the receiver to the server passing back their user ID. The server side code should then go over a hash table of sorts to find out who was trying to contact them (you also have the option of course of just passing around users' IDs so you just pass back the sender's ID too)
    6. Get the server to find the sender and respond appropriately.
    Check out some tutorials here that cover a lot of server side coding best practices:
    http://www.fmsguru.com/tutorials.cfm?tab=fms
    That kind of functionality is covered in our chat application product too, but it's not free unfortunately.
    Anyways, hope that helps with your question. It's a big deal building that kind of functionality in but can definitely be done with a bit of coding.

Maybe you are looking for