Per requests from users, I updated it to use a local version in the case your not connected. I failed my first test of the occasionally connected model, hence why I’m not on the beta. :: JD hangs head in disgust ::
Phat Clip!
Every so often, a component comes along that is not a frikin’ widget, but instead just one cool as hell movie clip. Here’s <a href=”http://flashcomponents.net/component.cfm?id=318&nav=2″>one of those</a> (via da <a href=”http://www.fullasagoog.com”>Goog</a>).
I’ve had it with Key.getCode
So, I made a tool to help me out. It gives you the key code, key ascii, and the character hit without you having to code a quick swf to find it yourself like I’ve had to do 50 million times. Off to the left, called “<a href=”https://www.jessewarden.com/downloads/JXL%20Key%20Tool.mxp”>JXL Key Tool</a>”. A Flash panel.
BTW, Anyone know how to size a Flash panel and/or access the top right drop down menu?
Function.call got shafted, yo
Is it just me, or is Function.call like a “Licker” from Resident Evil 2 and Function.apply like the final beast?
Seriously, Function.call is neat and all, but even though they advertise “…code that is concise and readable…” in the docs, to me, apply offers more concise code than call does. The only time I could think where I’d prefer to use call insead of apply is if I was creating arguments inside a function and didn’t have access to my arguments object to put them in.
<code>
function something(){
var arg1 = “moo”;
var arg2 = “wuzzup”;
this.otherFunction.call(_level2, arg1, arg2);
}
</code>
To me, there is no way to easily type in your arguments, unless you did:
<code>
this.otherFunction.apply(_level2, [arg1, arg2]);
</code>
Which certainly isn’t as readable. I still think <code>call</code> got shafted, though.