Brown

 to generate a UNIX timestamp on receiving a bang. Originally my code was identical to the JS posted in the linked thread, but the current version is below, after fiddling with it to try and debug some strange behavior:

inlets = 1;
outlets = 1;

var t = 0;

function bang() {
    var myDate = new Date();
    t = myDate.getTime();
    post("current time: " + t);
    post();
    outlet(0, t); // will send out the unix time in milliseconds when receiving a bang
}


If I connect any Max object (a dict, a message) to the [js] outlet to monitor the output, the timestamp does not update consistently. The first bang will occur just fine, but on subsequent bangs, the outlet value updates only if I wait ~40 seconds before clicking again. However, the Max Console 

 show an updated timestamp every time, so I'm not sure what's going on. I'd post the patch, but it's literally 

I'm borrowing code from this thread to generate a UNIX timestamp on receiving a bang. Originally my code was identical to the JS posted in the linked thread, but the current version is below, after fiddling with it to try and debug some strange behavior:

inlets = 1;
outlets = 1;

var t = 0;

function bang() {
	var myDate = new Date();
	t = myDate.getTime();
	post("current time: " + t);
	post();
	outlet(0, t); // will send out the unix time in milliseconds when receiving a bang
}


If I connect any Max object (a dict, a message) to the [js] outlet to monitor the output, the timestamp does not update consistently. The first bang will occur just fine, but on subsequent bangs, the outlet value updates only  if I wait ~40 seconds before clicking again. However, the Max Console does show an updated timestamp every time, so I'm not sure what's going on. I'd post the patch, but it's literally bang -> [js] -> message.


[js] outlet not updating values faithfully?