Event callbacks assigned through onevent attributes in innerHTML and outerHTML statements
When you use innerHTML or outerHTML to add elements to the DOM of a document, any event callbacks assigned within the statement, such as onclick or onmouseover, are ignored. No security error is generated. Instead, you can assign an id attribute to the new elements and set the event handler callback functions using the addEventListener() method.
For example, given a target element in a document, such as:
<div id="container"></div>
Replace statements such as:
document.getElementById('container').innerHTML =
'<a href="#" onclick="code()">Click Me</a>';
with:
document.getElementById('container').innerHTML = '<a href="#" id="smith">Click Me</a>';
smith = document.getElementById('smith');
if(smith!=null) smith.addEventListener("click", function() { code(); });
by Help Adobe
Templates variables:
$(EntryPoint) : cursor position
$(CSLB) (“Coding Style Line Break”) — when generating code, tells where to insert a linebreak if the “Coding Style Type” option (program setting) is set to “Brace After Line”.
General variables:
$(SelText) — selected text
$(CurWord) — word at cursor position
$(Clipboard) — clipboard content
$(Timestamp) — system time
$(CurFile) — current file
$(CurFilename) — current file’s name
$(CurDir) — current file’s directory
$(OpenFile) — show Open.. file dialog
$(SaveFile) — show Save As… file dialog
$(OpenDir) — show dialog to select a directory
$(DesktopDir) — user desktop directory
$(SystemDir) — Windows system directory
$(ProgramsDir) — Program Files directory
$(PersonalDir) — user directory
$(WorkingDir) — current working directory
$(AppDir) — FlashDevelop program directory
$(BaseDir) — FlashDevelop files
$(UserAppDir) — FlashDevelop user directory
Project related:
$(ToolsDir) — user Tools directory
$(OutputDir) — output file direcory
$(OutputName) — output file name
$(ProjectName) — project name
$(ProjectDir) — project directory
$(ProjectPath) — project file path
$(TypPkg) — File package
$(TypName) — Current type name
$(TypPkgName) — Current type qualified name (package+type name)
$(TypKind) — Type kind (interface, class)
$(MbrName) — Current member (declaration at line, ie. current method)
$(MbrKind) — Member kind (const, var, function)
$(MbrTypPkg) — Member’s type package
$(MbrTypName) — Members’s type name
$(MbrTypePkgName) — Members’s type qualified name (package+type name)
$(MbrTypKind) — Members’s type kind (interface, class)
$(ItmTypName) — Current item name (object resolved at cursor position)
$(ItmFile) — File where the item is declared
$(ItmKind) — Item kind (const, var, function)
$(ItmTypPkg) — Item’s type package
$(ItmTypName) — Item’s type name
$(ItmTypePkgName) — Item’s type qualified name (package+type name)
$(ItmTypKind) — Item’s type kind (interface, class)
by Philippe
“Unity is a multiplatform game development tool, designed from the start to ease creation. A fully integrated professional application, Unity just happens to contain the most powerful engine this side of a million dollars.” – unity3d.com
Según las últimas noticias en la nueva versión 3.0 añadirán la posibilidad de compilar para XBox, PlayStation3, iPad y Android.
