Kai O'Reilly
Kai O'Reilly
It is a very unfortunate situation, since it is impossible to fully avoid ambiguity given the US inconsistency, but we would probably try to comply with what each country uses...
OK, we can keep `Visible` as an uninherited state. Single-effect helper styler functions are a very slippery slope.
In the context of implementing this, we will also further develop the abilities and states docs with more explanations and examples for common abilities and states. We will also consider...
A summary of the current naming thinking: * `states.Displayable` instead of `states.Invisible`, with `WidgetBase.IsDisplayable` and `WidgetBase.IsVisible` helper functions (IsVisible checks the bounding box for actual visibility) * `abilities.Enabled` instead of...
We also need to update some of the language on deleting; for example, in file tree, it tells you that you are permanently deleting items even though they are moved...
@Bios-Marcel Yep, when I work on this, I plan to add it to wastebasket. It is not a high priority, but hopefully I will have the time at some point.
The issue here is that the gradient is updated in various places in `paint` based on the current bounding box, so somehow we need to inject the correct parent bounds...
The same thing applies for other non-uniform backgrounds, such as images.
#1389 did not fix this rare issue as discussed here: https://github.com/cogentcore/core/pull/1389#discussion_r1896472635.
See #1473 for the yaegicore part; this issue can be about expanding the standard icon set only.