summaryrefslogtreecommitdiff
path: root/editor/spatial_editor_gizmos.cpp
AgeCommit message (Collapse)Author
2019-09-25Merge pull request #32325 from SaracenOne/add_mesh_bindings_fixRémi Verschelde
SpatialEditorGizmo add_mesh bindings fix
2019-09-25Merge pull request #32119 from Calinou/unify-axis-colorsRémi Verschelde
Use the same axis colors consistently in the 2D and 3D editors
2019-09-25SpatialEditorGizmo add_mesh bindings fixSaracen
2019-09-24Improve the AudioStreamPlayer3D gizmoHugo Locurcio
This adds more lines to the emission angle cone to give a better feel of depth in the 3D world.
2019-09-24Fix wrong defval in EditorSpatialGizmo.add_mesh method bindIgnacio Etcheverry
The type of the parameter 'skeleton' was changed from 'RID' to 'SkinReference', yet the default value remained 'RID()'.
2019-09-23Merge pull request #32275 from godotengine/skin_supportRémi Verschelde
Added skin support and simplified APIs to override bone position + glTF 2.0 import fixes
2019-09-18Added skin support and simplified APIs to override bone position.Juan Linietsky
2019-09-17Improve the 3D light gizmosHugo Locurcio
OmniLight and SpotLight gizmos were tweaked to better represent their depth in the 3D world. The default light gizmo color was changed to match the gizmo icon color closely.
2019-09-13Use the same axis colors consistently in the 2D and 3D editorsHugo Locurcio
2019-08-21Draw 3D collision shape/raycast gizmos in grayscale when disabledHugo Locurcio
This makes them easier to distinguish from their enabled counterparts, as is already done in the 2D editor.
2019-08-08Add particles icon to CPUParticlesCameron Reikes
2019-07-03Implement snapping for most 3D gizmosHugo Locurcio
2019-07-01Remove unnecessary code and add some error explanationsqarmin
2019-06-26Some code changed with Clang-Tidyqarmin
2019-06-20Merge pull request #29283 from qarmin/fix_some_always_same_valuesRémi Verschelde
Remove always true/false values
2019-06-20Fix always true/false valuesqarmin
2019-06-03Add HeightMapShape mesh in CollisionShape gizmoJFonS
2019-05-08[EditorSpatialGizmo] Fix error in intersect_rayGuilherme Felipe
2019-04-23Merge pull request #26064 from JFonS/add_frustum_camera_modeHein-Pieter van Braam
Add FRUSTUM camera mode, allowing tilted frustums
2019-04-08Small fixes, mostly dupicated codeqarmin
2019-03-12Add priority to gizmos and fix small issuesJFonS
User defined gizmos will haave higher preference than editor gizmos by default. Also fixed some inconsistencies in the gizmos menu when using custom gizmos.
2019-02-25doc: Sync classref with current sourceRémi Verschelde
2019-02-24Fix default value of EditorSpatialGizmo.add_mesh method bindIgnacio Etcheverry
2019-02-23Remove copy and use instance material override in gizmos, fixes #23783Juan Linietsky
2019-02-20Add -Wshadow=local to warnings and fix reported issues.marxin
Fixes #25316.
2019-02-20Fix navigation editor color materials not having unique namesMichael Alexsander Silva Dias
2019-02-19Add FRUSTUM camera mode, allowing tilted frustumsJFonS
This new camera mode makes it easy to create tilted frustums for mirror or portal effects. This work was kindly sponsored by IMVU.
2019-02-08Fix undo for Particles 3D gizmoChaosus
2019-02-01Merge pull request #25540 from JFonS/remove_gizmo_errorsRémi Verschelde
Fix gizmo errors on "Align with view"
2019-02-01Fix gizmo errors on "Align with view"JFonS
2019-01-27Minor fixes and documentation for Spatial GizmosJFonS
2019-01-01Update copyright statements to 2019Rémi Verschelde
Happy new year to the wonderful Godot community!
2018-10-19Fixing warnings generated by MSVCDualtagh Murray
Fixes #22684.
2018-10-04Fix more "may be used initialized" warnings from GCC 7Rémi Verschelde
Fixes the following GCC 7 warnings: ``` core/cowdata.h:269:47: warning: 'alloc_size' may be used uninitialized in this function [-Wmaybe-uninitialized] core/error_macros.h:163:26: warning: 'nearest_point' may be used uninitialized in this function [-Wmaybe-uninitialized] core/image.cpp:1579:5: warning: 'colormap_size' may be used uninitialized in this function [-Wmaybe-uninitialized] core/image.cpp:1582:12: warning: 'size_height' may be used uninitialized in this function [-Wmaybe-uninitialized] core/image.cpp:1590:23: warning: 'size_width' may be used uninitialized in this function [-Wmaybe-uninitialized] core/image.cpp:1599:29: warning: 'pixel_size' may be used uninitialized in this function [-Wmaybe-uninitialized] core/math/face3.cpp:207:15: warning: 'tri_max' may be used uninitialized in this function [-Wmaybe-uninitialized] core/math/face3.cpp:209:15: warning: 'tri_min' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/gles3/rasterizer_scene_gles3.cpp:665:22: warning: 'best_used_frame' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/gles3/rasterizer_storage_gles3.cpp:865:27: warning: 'blit_target' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/gles3/rasterizer_storage_gles3.cpp:980:29: warning: 'blit_target' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/gles3/shader_gles3.h:122:9: warning: '<anonymous>.ShaderGLES3::Version::frag_id' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/gles3/shader_gles3.h:122:9: warning: '<anonymous>.ShaderGLES3::Version::id' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/gles3/shader_gles3.h:122:9: warning: '<anonymous>.ShaderGLES3::Version::vert_id' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/plugins/script_editor_plugin.cpp:1980:31: warning: 'se' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/scene_tree_dock.cpp:840:30: warning: 'new_node' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4259:9: warning: 'a1' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4259:9: warning: 'lll' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4259:9: warning: 'lul' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4260:9: warning: 'a2' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4261:9: warning: 'a3' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4265:3: warning: 'enable_lin' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4294:3: warning: 'enable_ang' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4311:34: warning: 'll' may be used uninitialized in this function [-Wmaybe-uninitialized] editor/spatial_editor_gizmos.cpp:4311:34: warning: 'ul' may be used uninitialized in this function [-Wmaybe-uninitialized] scene/3d/voxel_light_baker.cpp:1655:47: warning: 'cone_dirs' may be used uninitialized in this function [-Wmaybe-uninitialized] scene/3d/voxel_light_baker.cpp:1656:73: warning: 'cone_weights' may be used uninitialized in this function [-Wmaybe-uninitialized] scene/gui/texture_progress.cpp:181:6: warning: 'cp' may be used uninitialized in this function [-Wmaybe-uninitialized] scene/gui/texture_progress.cpp:181:6: warning: 'cq' may be used uninitialized in this function [-Wmaybe-uninitialized] servers/physics/shape_sw.cpp:1056:19: warning: 'support_max' may be used uninitialized in this function [-Wmaybe-uninitialized] ```
2018-09-27Fix warnings on non-static data member initializers (C++11 feature)Rémi Verschelde
We're not formally using C++11 yet so those trigger compilation warnings (at least with GCC 5): ./main/input_default.h:122:30: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 CursorShape default_shape = CURSOR_ARROW; ^ Note: We may allow those eventually (especially for non-int static const), but most of current occurrences were inconsistent with all other classes. See also http://www.stroustrup.com/C++11FAQ.html#member-init
2018-09-12Make core/ includes absolute, remove subfolders from include pathRémi Verschelde
This allows more consistency in the manner we include core headers, where previously there would be a mix of absolute, relative and include path-dependent includes.
2018-09-09Fix SoftBody gizmo slowness, add ConcaveShape wireframeJFonS
2018-09-05Merge pull request #21707 from JFonS/fix_instanced_selectionRémi Verschelde
Fix selection of instanced scenes in 3D
2018-09-04Move ParticlesMaterial code to its own resource fileRémi Verschelde
It's shared by both 2D and 3D particles (+ CPU ones), so it makes sense to have as a common resource. It also allowed to disable compilation of Particles (3D) when using 'disable_3d'. Also cleaned up includes in SpatialEditorGizmos and some other places, as well as dropped dead code in material_editor_plugin.cpp.
2018-09-02Fix selection of instanced scenes in 3DJFonS
2018-08-26Fixed physics bone crash: #20397Andrea Catania
2018-08-21Style: Fix issues that went past CIRémi Verschelde
2018-08-21Clipped camera implementation, a camera that avoids going into geometry.Juan Linietsky
2018-08-21Fix arg name in docs, some copy-paste errorsPoommetee Ketson
2018-08-18added spring arm node.QbieShay
2018-08-11Improvements on the gizmo disabling menu and icon selection bugfixJFonS
2018-08-09New gizmo structure and new gizmo disabling menuJFonS
2018-08-06Respect process order for out of order skeleton bones (fixes GLTF2 import ↵Juan Linietsky
issues).
2018-07-26Reduce unnecessary COW on Vector by make writing explicitHein-Pieter van Braam
This commit makes operator[] on Vector const and adds a write proxy to it. From now on writes to Vectors need to happen through the .write proxy. So for instance: Vector<int> vec; vec.push_back(10); std::cout << vec[0] << std::endl; vec.write[0] = 20; Failing to use the .write proxy will cause a compilation error. In addition COWable datatypes can now embed a CowData pointer to their data. This means that String, CharString, and VMap no longer use or derive from Vector. _ALWAYS_INLINE_ and _FORCE_INLINE_ are now equivalent for debug and non-debug builds. This is a lot faster for Vector in the editor and while running tests. The reason why this difference used to exist is because force-inlined methods used to give a bad debugging experience. After extensive testing with modern compilers this is no longer the case.
2018-07-23Implemented Soft bodyAndreaCatania
- Soft Body Physics node - Soft Body Rendering - Soft body Editor - Soft body importer