more progress on new eval/view-rule integration; raddbg_entry_point markup feature

This commit is contained in:
Ryan Fleury
2025-04-10 14:29:55 -07:00
parent ecb3992b93
commit da69d9e91c
9 changed files with 84 additions and 26 deletions
+2 -2
View File
@@ -10053,7 +10053,7 @@ rd_window_frame(void)
// rjf: hot effect extension
if(box->flags & UI_BoxFlag_DrawHotEffects)
{
B32 is_hot = ui_key_match(box->key, ui_hot_key());
B32 is_hot = !ui_key_match(box->key, ui_key_zero()) && ui_key_match(box->key, ui_hot_key());
Vec4F32 hover_color = ui_color_from_tags_key_name(box->tags_key, str8_lit("hover"));
// rjf: brighten
@@ -10264,7 +10264,7 @@ rd_window_frame(void)
if(b->flags & UI_BoxFlag_DrawHotEffects)
{
Vec4F32 color = ui_color_from_tags_key_name(box->tags_key, str8_lit("hover"));
if(!ui_key_match(b->key, ui_hot_key()))
if(ui_key_match(b->key, ui_key_zero()) || !ui_key_match(b->key, ui_hot_key()))
{
color.w *= b->hot_t;
}
+3
View File
@@ -78,6 +78,9 @@
// code. This is used by the debugger UI, but does not show up anywhere
// other than the source code, so it can either be used as a macro (which
// expands to nothing), or in comments too.
// - `raddbg_entry_point(name)`, e.g. `raddbg_entry_point(entry_point)`:
// declares the entry point for an executable, which the debugger will use
// when stepping into a program, rather than the defaults (e.g. `main`).
// - `raddbg_auto_view_rule(<type|pattern>, <view_rule>)`, e.g.
// `raddbg_auto_view_rule(DynamicArray<?>, slice)`: declares an
// auto-view-rule from source code, rather than from debugger