Skip to main content

jQuery dialog button variable



Can anyone tell me how can i use a varaible for button text in jQuery UI dialogs. I want to make a dynamic button name.





Source: Tips4all

Comments

  1. This won't work because of the way jQuery handles the button name (can be with or without quotes)

    This will work:


    var button_name = 'Test';

    var dialog_buttons = {};

    dialog_buttons[button_name] = function(){ closeInstanceForm(Function); }

    dialog_buttons['Cancel'] = function(){ $(this).dialog('close'); }

    $('#instanceDialog').dialog({ buttons: dialog_buttons });

    ReplyDelete
  2. The problem here is that the dialog plugin does not assign an id to its buttons, so it's quite difficult to modify them directly.

    Instead, initialise the dialog as normal, locate the button by the text it contains and add an id. The button can then be accessed directly to change the text, formatting, enable/disable it, etc.

    $("#dialog_box").dialog({
    buttons: {
    'ButtonA': function() {
    //... configure the button's function
    }
    });
    $('.ui-dialog-buttonpane button:contains(ButtonA)').attr("id","dialog_box_send-button");
    $('#dialog_box_send-button').html('Send')

    ReplyDelete
  3. What you can do is assign the button in the dialog an ID and then manipulate it using standard jQuery.

    $("#dialog_box").dialog({
    autoOpen: false,
    modal: true,
    resizable: false,
    buttons: [{
    text: "Ok",
    "id": "btnOk",
    click: function () {
    //okCallback();
    },

    }, {
    text: "Cancel",
    click: function () {
    //cancelCallback();
    },
    }],
    close: function () {
    //do something
    }
    });


    Set button text

    $("#btnOk").val("new label");

    ReplyDelete
  4. var buttonName = "something";
    $('#button-id').attr('value', buttonName);

    ReplyDelete
  5. This will work
    $($("button", $("#dialogId").parent())[NUMBER_OF_YOUR_BUTTON]).text("My Text");

    ReplyDelete
  6. And don't forget

    $($("button", $(".info_dialog").parent())[1]).html("<span class='ui-button-text'>Button text here.</span>");

    ReplyDelete
  7. Maybe I'm missing the point - but wouldn't the easiest way be to use the setter?

    $("#dialog_box").dialog({
    buttons: {
    [
    text:"OK",
    click: function() {
    //... configure the button's function
    }
    ]
    });

    $("#dialog_box").dialog("option", "buttons", { "Close": function() { $(this).dialog("close"); } });

    ReplyDelete
  8. assign a class to the button. The button text will be in a span with a class called ui-button-text inside your defined class.
    So if you give your button the class .contacts-dialog-search-button then the code to access the text will be:

    $('.ui-button-text','.contacts-dialog-search-button').text();


    here is the code I'm using for my current projects buttons, to give you an example.

    buttons : [
    {
    text : 'Advanced Search',
    click : function(){
    if($(this).dialog("option", "width")==290){
    $('#contacts-dialog-search').show();
    $(this).dialog("option", "width", 580);
    $('.ui-button-text','.contacts-dialog-search-button').text('Close Search');
    }
    else{
    $('#contacts-dialog-search').hide();
    $(this).dialog("option", "width", 290);
    $('.ui-button-text','.contacts-dialog-search-button').text('Advanced Search');
    }
    },
    "class" : "contacts-dialog-search-button"
    }
    ]

    ReplyDelete
  9. Yes completely possible with inline behaviour:


    Create Dialog class with two setter method, setYesButtonName() and setNoButtonName.




    function ConfirmDialog() {
    var yesButtonName = "Yes";
    var noButtonName = "No";
    this.showMessage = function(message, callback, argument) {
    var $dialog = $('<div></div>')
    .html(message)
    .dialog({
    modal: true,
    closeOnEscape: true,
    buttons: [
    {
    text:yesButtonName,
    click: function() {
    if (callback && typeof(callback) === "function") {
    if (argument == 'undefined') {
    callback();
    } else {
    callback(argument);
    }
    } else {
    $(this).dialog("close");
    }
    }
    },
    {
    text:noButtonName,
    click: function() {
    $(this).dialog("close");
    }

    }
    ]
    });
    $dialog.dialog("open");
    };

    this.setYesButtonName = function(name) {
    yesButtonName = name;
    return this;
    };

    this.setNoButtonName = function(name) {
    noButtonName = name;
    return this;
    };
    }





    Create Object of ConfirmDialog class.

    this.CONFIRM_DIALOG = new ConfirmDialog();

    Call method on any event, let's say onclick()

    OK_DIALOG.setYesButtonName('Wana Marry').showMessage('Worst Idea!!');



    Job Done!!

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex