Examples: DirectX9-10-11: Only call Windows' SetCursor(NULL) when io.MouseDrawCursor is set (#585, #909)

Fixing minor english typos (#827)

Examples: Accessing ImVector fields directly, feel less stl-ey and fix renderer side assert when render list only contains a callback (#810)

Examples; DirectX10/11: Added comments about removing dependency on d3dcompiler DLL (#638)

Examples: DirectX11: Fixed uninitialized fields. Disabling depth-write (#640, #636)

Examples: DirectX11: Fixed handle leak + minor coding style fix for #640

DX11 example depth test

Examples: DirectX10,DirectX11 : Minor renaming

Examples: DirectX11: Shallow massaging to make the code more consistent/readable (following #570)

Examples: DX11: Cleanup state backup/restore code (#570)

capture and restore all state

IO: Added "Super" keyboard modifiers (corresponding to Cmd on Mac and Windows key in theory although the later is hard to read) (#473) ...

NB: Value not used.

Trim trailing spaces

FAQ and comments about the use of ImTextureID (#562, #561, #521, #510, #497, #475 ...)

Examples: DirectX11: fixed ImGui_ImplDX11_NewFrame() from recreating device objects if render isn't called (g_pVB not set)

Examples: DirectX10: Minor tweaks, updated to latest example changes (#424)

Merge pull request #420 from RaptorFactor/master ...

Examples: DX11: Compile shaders with lower features levels.

Allow DX11 renderer to be used with devices with lower feature levels.

Examples: Not clearing input data/tex data in atlas (will be required for dynamic atlas anyway). Effectively fix resizing in DX examples. ...

+ Standardized comments.

Examples: Header comments.

Examples: Most examples apps detect if ImDrawIdx was changed to 32-bits instead of 16

Examples: Possibly clarified the intent of imgui_impl_* files.

fix POSITION format (ImDrawVert::pos is 2D, not 4D) ...

the inputlayout incorrectly described the POSITION attribute as being
4D, while ImDrawVert::pos is 2D. This went unnoticed because the buffer
binding has a stride of sizeof(ImDrawVert) and the POSITION is treated
as a float2 in the vertex shader. If you switch POSITION to float4 in
the vertex shader (and actually use the z/w in the matrix
multiplication) then everything become wacky-looking since it's
interpreting the texture coordinates as z/w. On a similar note: It's
weird that the projection matrix takes z and w into consideration when
those don't exist in the shader due to positions being float2s.

Examples: comment on setting the RenderDrawListsFn function.

Examples: DirectX11: fixed vertex shader which breaks with VS2015 somehow (DX11 version?) (#313)

Examples: DX9, DX11: mapping missing middle mouse button.

Examples: imgui_impl* functions declared with IMGUI_API to ease copy & pasting into projects using DLL

Examples: DirectX11: resizing buffers dynamically (#299)

Clear font texture view to ensure Release() doesn't get called twice

AA branch: Agressively renamed all fields of ImDrawList, ImDrawCmd, ImDrawData to match the rest of our coding convention (#133)