godotengine/godot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
d66eb77c9c
godot/scene/gui/texture_progress.cpp

557 lines
20 KiB
C++
Raw Normal View History

GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
/*************************************************************************/
/* texture_progress.cpp */
/*************************************************************************/
/* This file is part of: */
/* GODOT ENGINE */
Use HTTPS URL for Godot's website in the headers
2017-08-27 12:16:55 +00:00
/* https://godotengine.org */
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
/*************************************************************************/
Update copyright statements to 2020 Happy new year to the wonderful Godot community! We're starting a new decade with a well-established, non-profit, free and open source game engine, and tons of further improvements in the pipeline from hundreds of contributors. Godot will keep getting better, and we're looking forward to all the games that the community will keep developing and releasing with it.
2020-01-01 10:16:22 +00:00
/* Copyright (c) 2007-2020 Juan Linietsky, Ariel Manzur. */
/* Copyright (c) 2014-2020 Godot Engine contributors (cf. AUTHORS.md). */
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
/* */
/* Permission is hereby granted, free of charge, to any person obtaining */
/* a copy of this software and associated documentation files (the */
/* "Software"), to deal in the Software without restriction, including */
/* without limitation the rights to use, copy, modify, merge, publish, */
/* distribute, sublicense, and/or sell copies of the Software, and to */
/* permit persons to whom the Software is furnished to do so, subject to */
/* the following conditions: */
/* */
/* The above copyright notice and this permission notice shall be */
/* included in all copies or substantial portions of the Software. */
/* */
/* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, */
/* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF */
/* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.*/
/* IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY */
/* CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, */
/* TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE */
/* SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. */
/*************************************************************************/
Add missing copyright headers and fix formatting Using `misc/scripts/fix_headers.py` on all Godot files. Some missing header guards were added, and the header inclusion order was fixed in the Bullet module.
2018-01-04 23:50:27 +00:00
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
#include "texture_progress.h"
Reorganized core/ directory, it was too fatty already -Removed FuncRef, since Callable makes it obsolete -Removed int_types.h as its obsolete in c++11+ -Changed color names code
2020-11-07 22:33:38 +00:00
#include "core/config/engine.h"
Removes editor_hint from SceneTree
2017-08-18 23:02:56 +00:00
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
void TextureProgress::set_under_texture(const Ref<Texture2D> &p_texture) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
under = p_texture;
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
update();
minimum_size_changed();
}
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
Ref<Texture2D> TextureProgress::get_under_texture() const {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
return under;
}
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
void TextureProgress::set_over_texture(const Ref<Texture2D> &p_texture) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
over = p_texture;
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
update();
WIP new AudioServer, with buses, effects, etc.
2017-01-21 22:00:25 +00:00
if (under.is_null()) {
minimum_size_changed();
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
}
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
Ref<Texture2D> TextureProgress::get_over_texture() const {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
return over;
}
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
void TextureProgress::set_stretch_margin(Margin p_margin, int p_size) {
fix enum cast warnings on clang
2018-10-04 07:17:59 +00:00
ERR_FAIL_INDEX((int)p_margin, 4);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
stretch_margin[p_margin] = p_size;
update();
minimum_size_changed();
}
int TextureProgress::get_stretch_margin(Margin p_margin) const {
fix enum cast warnings on clang
2018-10-04 07:17:59 +00:00
ERR_FAIL_INDEX_V((int)p_margin, 4, 0);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
return stretch_margin[p_margin];
}
void TextureProgress::set_nine_patch_stretch(bool p_stretch) {
nine_patch_stretch = p_stretch;
update();
minimum_size_changed();
}
bool TextureProgress::get_nine_patch_stretch() const {
return nine_patch_stretch;
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
Size2 TextureProgress::get_minimum_size() const {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (nine_patch_stretch) {
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
return Size2(stretch_margin[MARGIN_LEFT] + stretch_margin[MARGIN_RIGHT], stretch_margin[MARGIN_TOP] + stretch_margin[MARGIN_BOTTOM]);
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
} else if (under.is_valid()) {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
return under->get_size();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
} else if (over.is_valid()) {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
return over->get_size();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
} else if (progress.is_valid()) {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
return progress->get_size();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
return Size2(1, 1);
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
}
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
void TextureProgress::set_progress_texture(const Ref<Texture2D> &p_texture) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
progress = p_texture;
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
update();
minimum_size_changed();
}
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
Ref<Texture2D> TextureProgress::get_progress_texture() const {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
return progress;
}
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
void TextureProgress::set_tint_under(const Color &p_tint) {
tint_under = p_tint;
update();
}
Color TextureProgress::get_tint_under() const {
return tint_under;
}
void TextureProgress::set_tint_progress(const Color &p_tint) {
tint_progress = p_tint;
update();
}
Color TextureProgress::get_tint_progress() const {
return tint_progress;
}
void TextureProgress::set_tint_over(const Color &p_tint) {
tint_over = p_tint;
update();
}
Color TextureProgress::get_tint_over() const {
return tint_over;
}
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
Point2 TextureProgress::unit_val_to_uv(float val) {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (progress.is_null()) {
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
return Point2();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (val < 0) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
val += 1;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
if (val > 1) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
val -= 1;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
Point2 p = get_relative_center();
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
// Minimal version of Liang-Barsky clipping algorithm
float angle = (val * Math_TAU) - Math_PI * 0.5;
Point2 dir = Vector2(Math::cos(angle), Math::sin(angle));
float t1 = 1.0;
Fix more "may be used initialized" warnings from GCC 7 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-10-04 16:54:20 +00:00
float cp = 0;
float cq = 0;
float cr = 0;
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
float edgeLeft = 0.0;
float edgeRight = 1.0;
float edgeBottom = 0.0;
float edgeTop = 1.0;
for (int edge = 0; edge < 4; edge++) {
if (edge == 0) {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (dir.x > 0) {
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
continue;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
cq = -(edgeLeft - p.x);
Fixed radial progress with center offset by taking distance to edge into account in uv calculation
2019-02-16 20:02:29 +00:00
dir.x *= 2.0 * cq;
cp = -dir.x;
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
} else if (edge == 1) {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (dir.x < 0) {
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
continue;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
cq = (edgeRight - p.x);
Fixed radial progress with center offset by taking distance to edge into account in uv calculation
2019-02-16 20:02:29 +00:00
dir.x *= 2.0 * cq;
cp = dir.x;
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
} else if (edge == 2) {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (dir.y > 0) {
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
continue;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
cq = -(edgeBottom - p.y);
Fixed radial progress with center offset by taking distance to edge into account in uv calculation
2019-02-16 20:02:29 +00:00
dir.y *= 2.0 * cq;
cp = -dir.y;
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
} else if (edge == 3) {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (dir.y < 0) {
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
continue;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
cq = (edgeTop - p.y);
Fixed radial progress with center offset by taking distance to edge into account in uv calculation
2019-02-16 20:02:29 +00:00
dir.y *= 2.0 * cq;
cp = dir.y;
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
}
cr = cq / cp;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (cr >= 0 && cr < t1) {
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
t1 = cr;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Implement line clipping for `TextureProgress` to avoid bad rendering due to imprecise UV mapping Original code used a quick aproximation for simulating the correspondent texel in the `TextureProgress` texture as radial progress indicator. This lead to visualization errors. Changed it for a Liang-Barsky line clipping algorithm stripped to its minimum for this specific use case. Fix #17364.
2018-03-10 19:51:42 +00:00
}
return (p + t1 * dir);
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
Point2 TextureProgress::get_relative_center() {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (progress.is_null()) {
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
return Point2();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
Point2 p = progress->get_size() / 2;
p += rad_center_off;
p.x /= progress->get_width();
p.y /= progress->get_height();
p.x = CLAMP(p.x, 0, 1);
p.y = CLAMP(p.y, 0, 1);
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
return p;
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
void TextureProgress::draw_nine_patch_stretched(const Ref<Texture2D> &p_texture, FillMode p_mode, double p_ratio, const Color &p_modulate) {
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
Vector2 texture_size = p_texture->get_size();
Vector2 topleft = Vector2(stretch_margin[MARGIN_LEFT], stretch_margin[MARGIN_TOP]);
Vector2 bottomright = Vector2(stretch_margin[MARGIN_RIGHT], stretch_margin[MARGIN_BOTTOM]);
Rect2 src_rect = Rect2(Point2(), texture_size);
Rect2 dst_rect = Rect2(Point2(), get_size());
if (p_ratio < 1.0) {
// Drawing a partially-filled 9-patch is a little tricky -
// texture is divided by 3 sections toward fill direction,
Fix typos with codespell Found via `codespell -q 3 --skip="./thirdparty,./editor/translations" -I ../godot-word-whitelist.txt` Whitelist consists of: ``` ang doubleclick lod nd que te unselect ```
2018-02-21 16:30:55 +00:00
// then middle section is stretching while the other two aren't.
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
double width_total = 0.0;
double width_texture = 0.0;
double first_section_size = 0.0;
double last_section_size = 0.0;
switch (mode) {
case FILL_LEFT_TO_RIGHT:
case FILL_RIGHT_TO_LEFT: {
width_total = dst_rect.size.x;
width_texture = texture_size.x;
first_section_size = topleft.x;
last_section_size = bottomright.x;
} break;
case FILL_TOP_TO_BOTTOM:
case FILL_BOTTOM_TO_TOP: {
width_total = dst_rect.size.y;
width_texture = texture_size.y;
first_section_size = topleft.y;
last_section_size = bottomright.y;
} break;
Fix warnings about unhandled enum value in switch [-Wswitch] Fixes GCC 5 warnings of the form: core/io/http_client.cpp:288:9: warning: enumeration value 'STATUS_SSL_HANDSHAKE_ERROR' not handled in switch [-Wswitch] core/io/marshalls.cpp:806:9: warning: enumeration value 'AABB' not handled in switch [-Wswitch] Those can be trivial cases where adding a default fallback is the solution, or more complex issues/hidden bugs where missed values are actually meant to be handled.
2018-09-26 11:13:56 +00:00
case FILL_BILINEAR_LEFT_AND_RIGHT: {
// TODO: Implement
} break;
case FILL_BILINEAR_TOP_AND_BOTTOM: {
// TODO: Implement
} break;
case FILL_CLOCKWISE:
case FILL_CLOCKWISE_AND_COUNTER_CLOCKWISE:
case FILL_COUNTER_CLOCKWISE: {
// Those modes are circular, not relevant for nine patch
} break;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
double width_filled = width_total * p_ratio;
double middle_section_size = MAX(0.0, width_texture - first_section_size - last_section_size);
middle_section_size *= MIN(1.0, (MAX(0.0, width_filled - first_section_size) / MAX(1.0, width_total - first_section_size - last_section_size)));
last_section_size = MAX(0.0, last_section_size - (width_total - width_filled));
Truncate first segment in TextureProgress 9slices Much in the way that TextureProgress was truncating the last segment of the nine slice when the value wasn't close to the end, perform similar work on the beginning segment. This fixes the beginning segment always being drawn, sometimes in the incorrect location.
2019-02-19 08:28:32 +00:00
first_section_size = MIN(first_section_size, width_filled);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
width_texture = MIN(width_texture, first_section_size + middle_section_size + last_section_size);
switch (mode) {
case FILL_LEFT_TO_RIGHT: {
src_rect.size.x = width_texture;
dst_rect.size.x = width_filled;
Truncate first segment in TextureProgress 9slices Much in the way that TextureProgress was truncating the last segment of the nine slice when the value wasn't close to the end, perform similar work on the beginning segment. This fixes the beginning segment always being drawn, sometimes in the incorrect location.
2019-02-19 08:28:32 +00:00
topleft.x = first_section_size;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
bottomright.x = last_section_size;
} break;
case FILL_RIGHT_TO_LEFT: {
src_rect.position.x += src_rect.size.x - width_texture;
src_rect.size.x = width_texture;
dst_rect.position.x += width_total - width_filled;
dst_rect.size.x = width_filled;
topleft.x = last_section_size;
Truncate first segment in TextureProgress 9slices Much in the way that TextureProgress was truncating the last segment of the nine slice when the value wasn't close to the end, perform similar work on the beginning segment. This fixes the beginning segment always being drawn, sometimes in the incorrect location.
2019-02-19 08:28:32 +00:00
bottomright.x = first_section_size;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
case FILL_TOP_TO_BOTTOM: {
src_rect.size.y = width_texture;
dst_rect.size.y = width_filled;
bottomright.y = last_section_size;
Truncate first segment in TextureProgress 9slices Much in the way that TextureProgress was truncating the last segment of the nine slice when the value wasn't close to the end, perform similar work on the beginning segment. This fixes the beginning segment always being drawn, sometimes in the incorrect location.
2019-02-19 08:28:32 +00:00
topleft.y = first_section_size;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
case FILL_BOTTOM_TO_TOP: {
src_rect.position.y += src_rect.size.y - width_texture;
src_rect.size.y = width_texture;
dst_rect.position.y += width_total - width_filled;
dst_rect.size.y = width_filled;
topleft.y = last_section_size;
Truncate first segment in TextureProgress 9slices Much in the way that TextureProgress was truncating the last segment of the nine slice when the value wasn't close to the end, perform similar work on the beginning segment. This fixes the beginning segment always being drawn, sometimes in the incorrect location.
2019-02-19 08:28:32 +00:00
bottomright.y = first_section_size;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
Fix warnings about unhandled enum value in switch [-Wswitch] Fixes GCC 5 warnings of the form: core/io/http_client.cpp:288:9: warning: enumeration value 'STATUS_SSL_HANDSHAKE_ERROR' not handled in switch [-Wswitch] core/io/marshalls.cpp:806:9: warning: enumeration value 'AABB' not handled in switch [-Wswitch] Those can be trivial cases where adding a default fallback is the solution, or more complex issues/hidden bugs where missed values are actually meant to be handled.
2018-09-26 11:13:56 +00:00
case FILL_BILINEAR_LEFT_AND_RIGHT: {
// TODO: Implement
} break;
case FILL_BILINEAR_TOP_AND_BOTTOM: {
// TODO: Implement
} break;
case FILL_CLOCKWISE:
case FILL_CLOCKWISE_AND_COUNTER_CLOCKWISE:
case FILL_COUNTER_CLOCKWISE: {
// Those modes are circular, not relevant for nine patch
} break;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
}
Fix AtlasTexture with NinePatchRect and TextureProgress
2018-08-18 15:37:50 +00:00
p_texture->get_rect_region(dst_rect, src_rect, dst_rect, src_rect);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
RID ci = get_canvas_item();
Renaming of servers for coherency. VisualServer -> RenderingServer PhysicsServer -> PhysicsServer3D Physics2DServer -> PhysicsServer2D NavigationServer -> NavigationServer3D Navigation2DServer -> NavigationServer2D Also renamed corresponding files.
2020-03-27 18:21:27 +00:00
RS::get_singleton()->canvas_item_add_nine_patch(ci, dst_rect, src_rect, p_texture->get_rid(), topleft, bottomright, RS::NINE_PATCH_STRETCH, RS::NINE_PATCH_STRETCH, true, p_modulate);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
void TextureProgress::_notification(int p_what) {
const float corners[12] = { -0.125, -0.375, -0.625, -0.875, 0.125, 0.375, 0.625, 0.875, 1.125, 1.375, 1.625, 1.875 };
switch (p_what) {
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
case NOTIFICATION_DRAW: {
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
if (nine_patch_stretch && (mode == FILL_LEFT_TO_RIGHT || mode == FILL_RIGHT_TO_LEFT || mode == FILL_TOP_TO_BOTTOM || mode == FILL_BOTTOM_TO_TOP)) {
if (under.is_valid()) {
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_nine_patch_stretched(under, FILL_LEFT_TO_RIGHT, 1.0, tint_under);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
if (progress.is_valid()) {
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_nine_patch_stretched(progress, mode, get_as_ratio(), tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
if (over.is_valid()) {
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_nine_patch_stretched(over, FILL_LEFT_TO_RIGHT, 1.0, tint_over);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
} else {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (under.is_valid()) {
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture(under, Point2(), tint_under);
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
if (progress.is_valid()) {
Size2 s = progress->get_size();
switch (mode) {
case FILL_LEFT_TO_RIGHT: {
Rect2 region = Rect2(Point2(), Size2(s.x * get_as_ratio(), s.y));
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture_rect_region(progress, region, region, tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
case FILL_RIGHT_TO_LEFT: {
Rect2 region = Rect2(Point2(s.x - s.x * get_as_ratio(), 0), Size2(s.x * get_as_ratio(), s.y));
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture_rect_region(progress, region, region, tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
case FILL_TOP_TO_BOTTOM: {
Rect2 region = Rect2(Point2(), Size2(s.x, s.y * get_as_ratio()));
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture_rect_region(progress, region, region, tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
case FILL_BOTTOM_TO_TOP: {
Rect2 region = Rect2(Point2(0, s.y - s.y * get_as_ratio()), Size2(s.x, s.y * get_as_ratio()));
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture_rect_region(progress, region, region, tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
case FILL_CLOCKWISE:
Add support for bilinear bars in TextureProgress These bars will extend from the center to the left and right of the node, or from the center to the top and bottom of the node depending on the option selected. The Clockwise and Counter Clockwise mode will expand the progress bar both ways in a circular fashion.
2018-05-11 17:44:05 +00:00
case FILL_COUNTER_CLOCKWISE:
case FILL_CLOCKWISE_AND_COUNTER_CLOCKWISE: {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (nine_patch_stretch) {
Make TextureProgress's nine_patch_stretch property to enable stretching for radial fills.
2019-09-26 09:46:07 +00:00
s = get_size();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Make TextureProgress's nine_patch_stretch property to enable stretching for radial fills.
2019-09-26 09:46:07 +00:00
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
float val = get_as_ratio() * rad_max_degrees / 360;
if (val == 1) {
Rect2 region = Rect2(Point2(), s);
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture_rect_region(progress, region, region, tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} else if (val != 0) {
Array pts;
Add support for bilinear bars in TextureProgress These bars will extend from the center to the left and right of the node, or from the center to the top and bottom of the node depending on the option selected. The Clockwise and Counter Clockwise mode will expand the progress bar both ways in a circular fashion.
2018-05-11 17:44:05 +00:00
float direction = mode == FILL_COUNTER_CLOCKWISE ? -1 : 1;
float start;
if (mode == FILL_CLOCKWISE_AND_COUNTER_CLOCKWISE) {
start = rad_init_angle / 360 - val / 2;
} else {
start = rad_init_angle / 360;
}
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
float end = start + direction * val;
pts.append(start);
pts.append(end);
float from = MIN(start, end);
float to = MAX(start, end);
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
for (int i = 0; i < 12; i++) {
if (corners[i] > from && corners[i] < to) {
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
pts.append(corners[i]);
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
}
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
pts.sort();
Vector<Point2> uvs;
Vector<Point2> points;
uvs.push_back(get_relative_center());
points.push_back(Point2(s.x * get_relative_center().x, s.y * get_relative_center().y));
for (int i = 0; i < pts.size(); i++) {
Point2 uv = unit_val_to_uv(pts[i]);
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (uvs.find(uv) >= 0) {
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
continue;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
uvs.push_back(uv);
points.push_back(Point2(uv.x * s.x, uv.y * s.y));
}
add tint property to TextureProgress changes progress color
2018-03-21 18:55:39 +00:00
Vector<Color> colors;
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
colors.push_back(tint_progress);
add tint property to TextureProgress changes progress color
2018-03-21 18:55:39 +00:00
draw_polygon(points, colors, uvs, progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
if (Engine::get_singleton()->is_editor_hint()) {
Make TextureProgress's nine_patch_stretch property to enable stretching for radial fills.
2019-09-26 09:46:07 +00:00
Point2 p;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (nine_patch_stretch) {
Make TextureProgress's nine_patch_stretch property to enable stretching for radial fills.
2019-09-26 09:46:07 +00:00
p = get_size();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
} else {
Make TextureProgress's nine_patch_stretch property to enable stretching for radial fills.
2019-09-26 09:46:07 +00:00
p = progress->get_size();
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
Make TextureProgress's nine_patch_stretch property to enable stretching for radial fills.
2019-09-26 09:46:07 +00:00
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
p.x *= get_relative_center().x;
p.y *= get_relative_center().y;
p = p.floor();
draw_line(p - Point2(8, 0), p + Point2(8, 0), Color(0.9, 0.5, 0.5), 2);
draw_line(p - Point2(0, 8), p + Point2(0, 8), Color(0.9, 0.5, 0.5), 2);
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
}
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
} break;
Add support for bilinear bars in TextureProgress These bars will extend from the center to the left and right of the node, or from the center to the top and bottom of the node depending on the option selected. The Clockwise and Counter Clockwise mode will expand the progress bar both ways in a circular fashion.
2018-05-11 17:44:05 +00:00
case FILL_BILINEAR_LEFT_AND_RIGHT: {
Rect2 region = Rect2(Point2(s.x / 2 - s.x * get_as_ratio() / 2, 0), Size2(s.x * get_as_ratio(), s.y));
draw_texture_rect_region(progress, region, region, tint_progress);
} break;
case FILL_BILINEAR_TOP_AND_BOTTOM: {
Rect2 region = Rect2(Point2(0, s.y / 2 - s.y * get_as_ratio() / 2), Size2(s.x, s.y * get_as_ratio()));
draw_texture_rect_region(progress, region, region, tint_progress);
} break;
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
default:
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture_rect_region(progress, Rect2(Point2(), Size2(s.x * get_as_ratio(), s.y)), Rect2(Point2(), Size2(s.x * get_as_ratio(), s.y)), tint_progress);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
}
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
}
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
if (over.is_valid()) {
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
draw_texture(over, Point2(), tint_over);
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
}
} break;
}
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
void TextureProgress::set_fill_mode(int p_fill) {
Add support for bilinear bars in TextureProgress These bars will extend from the center to the left and right of the node, or from the center to the top and bottom of the node depending on the option selected. The Clockwise and Counter Clockwise mode will expand the progress bar both ways in a circular fashion.
2018-05-11 17:44:05 +00:00
ERR_FAIL_INDEX(p_fill, 9);
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
mode = (FillMode)p_fill;
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
update();
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
int TextureProgress::get_fill_mode() {
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
return mode;
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
void TextureProgress::set_radial_initial_angle(float p_angle) {
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
while (p_angle > 360) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
p_angle -= 360;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
while (p_angle < 0) {
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
p_angle += 360;
Style: Enforce braces around if blocks and loops Using clang-tidy's `readability-braces-around-statements`. https://clang.llvm.org/extra/clang-tidy/checks/readability-braces-around-statements.html
2020-05-14 14:41:43 +00:00
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
rad_init_angle = p_angle;
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
update();
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
float TextureProgress::get_radial_initial_angle() {
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
return rad_init_angle;
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
void TextureProgress::set_fill_degrees(float p_angle) {
rad_max_degrees = CLAMP(p_angle, 0, 360);
Add fill_degrees to limitate radial filling
2015-10-18 04:21:53 +00:00
update();
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
float TextureProgress::get_fill_degrees() {
Add fill_degrees to limitate radial filling
2015-10-18 04:21:53 +00:00
return rad_max_degrees;
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
void TextureProgress::set_radial_center_offset(const Point2 &p_off) {
rad_center_off = p_off;
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
update();
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
Point2 TextureProgress::get_radial_center_offset() {
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
return rad_center_off;
}
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
void TextureProgress::_bind_methods() {
Removes type information from method binds
2017-08-09 11:19:41 +00:00
ClassDB::bind_method(D_METHOD("set_under_texture", "tex"), &TextureProgress::set_under_texture);
ClassDB::bind_method(D_METHOD("get_under_texture"), &TextureProgress::get_under_texture);
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
Removes type information from method binds
2017-08-09 11:19:41 +00:00
ClassDB::bind_method(D_METHOD("set_progress_texture", "tex"), &TextureProgress::set_progress_texture);
ClassDB::bind_method(D_METHOD("get_progress_texture"), &TextureProgress::get_progress_texture);
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
Removes type information from method binds
2017-08-09 11:19:41 +00:00
ClassDB::bind_method(D_METHOD("set_over_texture", "tex"), &TextureProgress::set_over_texture);
ClassDB::bind_method(D_METHOD("get_over_texture"), &TextureProgress::get_over_texture);
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ClassDB::bind_method(D_METHOD("set_fill_mode", "mode"), &TextureProgress::set_fill_mode);
Rename the _MD macro to D_METHOD This new name also makes its purpose a little clearer This is a step towards fixing #56
2017-02-13 11:47:24 +00:00
ClassDB::bind_method(D_METHOD("get_fill_mode"), &TextureProgress::get_fill_mode);
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
ClassDB::bind_method(D_METHOD("set_tint_under", "tint"), &TextureProgress::set_tint_under);
ClassDB::bind_method(D_METHOD("get_tint_under"), &TextureProgress::get_tint_under);
ClassDB::bind_method(D_METHOD("set_tint_progress", "tint"), &TextureProgress::set_tint_progress);
ClassDB::bind_method(D_METHOD("get_tint_progress"), &TextureProgress::get_tint_progress);
ClassDB::bind_method(D_METHOD("set_tint_over", "tint"), &TextureProgress::set_tint_over);
ClassDB::bind_method(D_METHOD("get_tint_over"), &TextureProgress::get_tint_over);
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ClassDB::bind_method(D_METHOD("set_radial_initial_angle", "mode"), &TextureProgress::set_radial_initial_angle);
Rename the _MD macro to D_METHOD This new name also makes its purpose a little clearer This is a step towards fixing #56
2017-02-13 11:47:24 +00:00
ClassDB::bind_method(D_METHOD("get_radial_initial_angle"), &TextureProgress::get_radial_initial_angle);
remove trailing whitespace
2016-03-08 23:00:52 +00:00
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ClassDB::bind_method(D_METHOD("set_radial_center_offset", "mode"), &TextureProgress::set_radial_center_offset);
Rename the _MD macro to D_METHOD This new name also makes its purpose a little clearer This is a step towards fixing #56
2017-02-13 11:47:24 +00:00
ClassDB::bind_method(D_METHOD("get_radial_center_offset"), &TextureProgress::get_radial_center_offset);
remove trailing whitespace
2016-03-08 23:00:52 +00:00
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ClassDB::bind_method(D_METHOD("set_fill_degrees", "mode"), &TextureProgress::set_fill_degrees);
Rename the _MD macro to D_METHOD This new name also makes its purpose a little clearer This is a step towards fixing #56
2017-02-13 11:47:24 +00:00
ClassDB::bind_method(D_METHOD("get_fill_degrees"), &TextureProgress::get_fill_degrees);
Add fill modes. Clockwise, Counter-CW and center-offset
2015-10-18 02:37:39 +00:00
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
ClassDB::bind_method(D_METHOD("set_stretch_margin", "margin", "value"), &TextureProgress::set_stretch_margin);
ClassDB::bind_method(D_METHOD("get_stretch_margin", "margin"), &TextureProgress::get_stretch_margin);
ClassDB::bind_method(D_METHOD("set_nine_patch_stretch", "stretch"), &TextureProgress::set_nine_patch_stretch);
ClassDB::bind_method(D_METHOD("get_nine_patch_stretch"), &TextureProgress::get_nine_patch_stretch);
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ADD_GROUP("Textures", "texture_");
Texture refactor -Texture renamed to Texture2D -TextureLayered as base now inherits 2Darray, cubemap and cubemap array -Removed all references to flags in textures (they will go in the shader) -Texture3D gone for now (will come back later done properly) -Create base rasterizer for RenderDevice, RasterizerRD
2019-06-11 18:43:37 +00:00
ADD_PROPERTY(PropertyInfo(Variant::OBJECT, "texture_under", PROPERTY_HINT_RESOURCE_TYPE, "Texture2D"), "set_under_texture", "get_under_texture");
ADD_PROPERTY(PropertyInfo(Variant::OBJECT, "texture_over", PROPERTY_HINT_RESOURCE_TYPE, "Texture2D"), "set_over_texture", "get_over_texture");
ADD_PROPERTY(PropertyInfo(Variant::OBJECT, "texture_progress", PROPERTY_HINT_RESOURCE_TYPE, "Texture2D"), "set_progress_texture", "get_progress_texture");
-Moved EditorDefaultValue to ClassDB, made it core -Removed one and zero hints for properties, replaced by default value
2018-11-08 14:30:02 +00:00
ADD_PROPERTY(PropertyInfo(Variant::INT, "fill_mode", PROPERTY_HINT_ENUM, "Left to Right,Right to Left,Top to Bottom,Bottom to Top,Clockwise,Counter Clockwise,Bilinear (Left and Right),Bilinear (Top and Bottom), Clockwise and Counter Clockwise"), "set_fill_mode", "get_fill_mode");
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
ADD_GROUP("Tint", "tint_");
Allow transparent colors in TextureProgress tint properties
2018-09-01 11:14:05 +00:00
ADD_PROPERTY(PropertyInfo(Variant::COLOR, "tint_under"), "set_tint_under", "get_tint_under");
ADD_PROPERTY(PropertyInfo(Variant::COLOR, "tint_over"), "set_tint_over", "get_tint_over");
ADD_PROPERTY(PropertyInfo(Variant::COLOR, "tint_progress"), "set_tint_progress", "get_tint_progress");
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ADD_GROUP("Radial Fill", "radial_");
Variant: Added 64-bit packed arrays, renamed Variant::REAL to FLOAT. - Renames PackedIntArray to PackedInt32Array. - Renames PackedFloatArray to PackedFloat32Array. - Adds PackedInt64Array and PackedFloat64Array. - Renames Variant::REAL to Variant::FLOAT for consistency. Packed arrays are for storing large amount of data and creating stuff like meshes, buffers. textures, etc. Forcing them to be 64 is a huge waste of memory. That said, many users requested the ability to have 64 bits packed arrays for their games, so this is just an optional added type. For Variant, the float datatype is always 64 bits, and exposed as `float`. We still have `real_t` which is the datatype that can change from 32 to 64 bits depending on a compile flag (not entirely working right now, but that's the idea). It affects math related datatypes and code only. Neither Variant nor PackedArray make use of real_t, which is only intended for math precision, so the term is removed from there to keep only float.
2020-02-24 18:20:53 +00:00
ADD_PROPERTY(PropertyInfo(Variant::FLOAT, "radial_initial_angle", PROPERTY_HINT_RANGE, "0.0,360.0,0.1,slider"), "set_radial_initial_angle", "get_radial_initial_angle");
ADD_PROPERTY(PropertyInfo(Variant::FLOAT, "radial_fill_degrees", PROPERTY_HINT_RANGE, "0.0,360.0,0.1,slider"), "set_fill_degrees", "get_fill_degrees");
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ADD_PROPERTY(PropertyInfo(Variant::VECTOR2, "radial_center_offset"), "set_radial_center_offset", "get_radial_center_offset");
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
ADD_GROUP("Stretch", "stretch_");
ADD_PROPERTY(PropertyInfo(Variant::BOOL, "nine_patch_stretch"), "set_nine_patch_stretch", "get_nine_patch_stretch");
-Moved EditorDefaultValue to ClassDB, made it core -Removed one and zero hints for properties, replaced by default value
2018-11-08 14:30:02 +00:00
ADD_PROPERTYI(PropertyInfo(Variant::INT, "stretch_margin_left", PROPERTY_HINT_RANGE, "0,16384,1"), "set_stretch_margin", "get_stretch_margin", MARGIN_LEFT);
ADD_PROPERTYI(PropertyInfo(Variant::INT, "stretch_margin_top", PROPERTY_HINT_RANGE, "0,16384,1"), "set_stretch_margin", "get_stretch_margin", MARGIN_TOP);
ADD_PROPERTYI(PropertyInfo(Variant::INT, "stretch_margin_right", PROPERTY_HINT_RANGE, "0,16384,1"), "set_stretch_margin", "get_stretch_margin", MARGIN_RIGHT);
ADD_PROPERTYI(PropertyInfo(Variant::INT, "stretch_margin_bottom", PROPERTY_HINT_RANGE, "0,16384,1"), "set_stretch_margin", "get_stretch_margin", MARGIN_BOTTOM);
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
ClassDB: Provide the enum name of integer constants
2017-08-20 15:45:01 +00:00
BIND_ENUM_CONSTANT(FILL_LEFT_TO_RIGHT);
BIND_ENUM_CONSTANT(FILL_RIGHT_TO_LEFT);
BIND_ENUM_CONSTANT(FILL_TOP_TO_BOTTOM);
BIND_ENUM_CONSTANT(FILL_BOTTOM_TO_TOP);
BIND_ENUM_CONSTANT(FILL_CLOCKWISE);
BIND_ENUM_CONSTANT(FILL_COUNTER_CLOCKWISE);
Add support for bilinear bars in TextureProgress These bars will extend from the center to the left and right of the node, or from the center to the top and bottom of the node depending on the option selected. The Clockwise and Counter Clockwise mode will expand the progress bar both ways in a circular fashion.
2018-05-11 17:44:05 +00:00
BIND_ENUM_CONSTANT(FILL_BILINEAR_LEFT_AND_RIGHT);
BIND_ENUM_CONSTANT(FILL_BILINEAR_TOP_AND_BOTTOM);
BIND_ENUM_CONSTANT(FILL_CLOCKWISE_AND_COUNTER_CLOCKWISE);
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
}
A Whole New World (clang-format edition) I can show you the code Pretty, with proper whitespace Tell me, coder, now when did You last write readable code? I can open your eyes Make you see your bad indent Force you to respect the style The core devs agreed upon A whole new world A new fantastic code format A de facto standard With some sugar Enforced with clang-format A whole new world A dazzling style we all dreamed of And when we read it through It's crystal clear That now we're in a whole new world of code
2017-03-05 15:44:50 +00:00
TextureProgress::TextureProgress() {
mode = FILL_LEFT_TO_RIGHT;
rad_init_angle = 0;
rad_center_off = Point2();
rad_max_degrees = 360;
WIP new AudioServer, with buses, effects, etc.
2017-01-21 22:00:25 +00:00
set_mouse_filter(MOUSE_FILTER_PASS);
Add stretching to `TextureProgress` Now `TextureProgress` has `nine_patch_stretch` flag. With this flag enabled, it's being rendered as 9-path using `stretch_margin_*` properties as texture margins. Stretching doesn't support `FILL_CLOCKWISE` and `FILL_COUNTER_CLOCKWISE` fill modes.
2017-08-21 04:01:06 +00:00
nine_patch_stretch = false;
stretch_margin[MARGIN_LEFT] = 0;
stretch_margin[MARGIN_RIGHT] = 0;
stretch_margin[MARGIN_BOTTOM] = 0;
stretch_margin[MARGIN_TOP] = 0;
add tint property to TextureProgress changes progress color
2018-03-21 18:55:39 +00:00
add tint for under, progress and over and tint group
2018-04-01 16:22:51 +00:00
tint_under = tint_progress = tint_over = Color(1, 1, 1);
GODOT IS OPEN SOURCE
2014-02-10 01:10:30 +00:00
}
Reference in New Issue Copy Permalink