| .. |
|
guiArrayCtrl.cpp
|
539efcb1e1
Input event changes
|
13 年 前 |
|
guiArrayCtrl.h
|
7dbfe6994d
Engine directory for ticket #1
|
13 年 前 |
|
guiCanvas.cpp
|
b4a1d18f42
Core implementation of Physical Based Rendering.
|
7 年 前 |
|
guiCanvas.h
|
40fff8ef50
Stabilizes the add/remove behavior of menubars by also tracking the modeless background control the menubars use for proper cleanup as well.
|
8 年 前 |
|
guiControl.cpp
|
79c34c68db
Use strncpy instead of strcpy because again, buffer overflows
|
7 年 前 |
|
guiControl.h
|
9d547537fd
canvas -- Added a way for a child control to handle an event but still have GuiCanvas::processInputEvent() return false, therefore allowing the event to also be handled by the ActionMap. (see DemoGame::processInputEvent()) . Also added methods for clearing "down" status of mouse buttons in cases where ActionMap grabs the mouse for dragging and masks the up events from GuiCanvas.
|
8 年 前 |
|
guiDefaultControlRender.cpp
|
2002d74b78
Issue found with PVS-Studio:
|
10 年 前 |
|
guiDefaultControlRender.h
|
7dbfe6994d
Engine directory for ticket #1
|
13 年 前 |
|
guiOffscreenCanvas.cpp
|
25686ed4be
Implementation of sRGB image support. Overhauls the linearization setup to utilize the sRGB image types, as well as refactors the use of ColorF and ColorI to be properly internally consistent. ColorIs are used only for front-facing/editing/UI settings, and ColorFs, now renamed to LinearColorF to reduce confusion of purpose, are used for color info in the engine itself. This avoids confusing and expensive conversions back and forth between types and avoids botches with linearity. Majority work done by @rextimmy
|
8 年 前 |
|
guiOffscreenCanvas.h
|
8b43ff3465
Update guiOffscreenCanvas.h
|
9 年 前 |
|
guiScriptNotifyControl.cpp
|
7dbfe6994d
Engine directory for ticket #1
|
13 年 前 |
|
guiScriptNotifyControl.h
|
7dbfe6994d
Engine directory for ticket #1
|
13 年 前 |
|
guiTypes.cpp
|
25686ed4be
Implementation of sRGB image support. Overhauls the linearization setup to utilize the sRGB image types, as well as refactors the use of ColorF and ColorI to be properly internally consistent. ColorIs are used only for front-facing/editing/UI settings, and ColorFs, now renamed to LinearColorF to reduce confusion of purpose, are used for color info in the engine itself. This avoids confusing and expensive conversions back and forth between types and avoids botches with linearity. Majority work done by @rextimmy
|
8 年 前 |
|
guiTypes.h
|
3ca67b3148
Update guiTypes.h
|
10 年 前 |
Areloch
b4a1d18f42
Core implementation of Physical Based Rendering.