Asked  7 Months ago    Answers:  5   Viewed   38 times

All I need to do is to execute a callback function when my current function execution ends.

function LoadData() 
    alert('The data has been loaded');
    //Call my callback with parameters. For example,
    //callback(loadedData , currentObject);

A consumer for this function should be like this:


function success(loadedData , currentObject) 
  //Todo: some action here 

How do I implement this?



Actually, your code will pretty much work as is, just declare your callback as an argument and you can call it directly using the argument name.

The basics

function doSomething(callback) {
    // ...

    // Call the callback
    callback('stuff', 'goes', 'here');

function foo(a, b, c) {
    // I'm the callback
    alert(a + " " + b + " " + c);


That will call doSomething, which will call foo, which will alert "stuff goes here".

Note that it's very important to pass the function reference (foo), rather than calling the function and passing its result (foo()). In your question, you do it properly, but it's just worth pointing out because it's a common error.

More advanced stuff

Sometimes you want to call the callback so it sees a specific value for this. You can easily do that with the JavaScript call function:

function Thing(name) { = name;
Thing.prototype.doSomething = function(callback) {
    // Call our callback, but using our own instance as the context;

function foo() {

var t = new Thing('Joe');
t.doSomething(foo);  // Alerts "Joe" via `foo`

You can also pass arguments:

function Thing(name) { = name;
Thing.prototype.doSomething = function(callback, salutation) {
    // Call our callback, but using our own instance as the context, salutation);

function foo(salutation) {
    alert(salutation + " " +;

var t = new Thing('Joe');
t.doSomething(foo, 'Hi');  // Alerts "Hi Joe" via `foo`

Sometimes it's useful to pass the arguments you want to give the callback as an array, rather than individually. You can use apply to do that:

function Thing(name) { = name;
Thing.prototype.doSomething = function(callback) {
    // Call our callback, but using our own instance as the context
    callback.apply(this, ['Hi', 3, 2, 1]);

function foo(salutation, three, two, one) {
    alert(salutation + " " + + " - " + three + " " + two + " " + one);

var t = new Thing('Joe');
t.doSomething(foo);  // Alerts "Hi Joe - 3 2 1" via `foo`
Tuesday, June 1, 2021
answered 7 Months ago
var input = document.createElement("input");

input.setAttribute("type", "hidden");

input.setAttribute("name", "name_you_want");

input.setAttribute("value", "value_you_want");

//append to form element that you want .
Wednesday, June 23, 2021
answered 6 Months ago

It's because the closure captures the variable i itself, not the current value. Try:

for (var i = 0; i < a.length; i++) (function(i)
    calcRoute(fixedLocation, my_cities[i].address, function(response) {

        // i want here to have the current "i" here


}) (i);

which will create a new i variable for each loop iteration.

Wednesday, August 11, 2021
answered 4 Months ago

After few more hours of experiments, I think, I've found a viable solution for my problem.

The point is to reference jQuery from parent window and trigger a jQuery event on this window (I'm a Mac user but I suppose, jQuery has events working cross-platform, so IE compatibility is not an issue here).

This is my code for click handler on anchor...

$(this).find('a[x-special="select-asset"]').click(function() {
    var evt = jQuery.Event('assetSelect', {
        url:        'this is url',
        closePopup: true,
    var _parent = window.opener;

... and this is the code of event handler:

$(document).bind('assetSelect', function (evt) {

This solution is fine, if you don't need to distinguish between multiple instances of the asset selection windows (only one window will dispatch "assetSelect" event). I have not found a way to pass a kind of tag parameter to window and then pass it back in event.

Because of this, I've chosen to go along with (at the end, better and visually more pleasant) solution, Fancybox. Unfortunately, there is no way - by default - to distinguish between instances either. Therefore, I've extended Fancybox as I've described in my blog post. I'm not including the full text of blog post here, because is not the topic of this question.

URL of the blog post:

Friday, October 22, 2021
answered 1 Month ago

You should use kubectl create to create your CR with generateName.

"kubectl apply will verify the existence of the resources before take action. If the resources do not exist, it will firstly create them. If use generateName, the resource name is not yet generated when verify the existence of the resource." source

Monday, November 22, 2021
answered 1 Week ago
Only authorized users can answer the question. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :