| |interface Efl.Text_Style @beta | |├ (P) text_color | |├ (P) text_background_type | |├ (P) text_background_color | |├ (P) text_underline_type | |├ (P) text_underline_color | |├ (P) text_underline_height | |├ (P) text_underline_dashed_color | |├ (P) text_underline_dashed_width | |├ (P) text_underline_dashed_gap | |├ (P) text_secondary_underline_color | |├ (P) text_strikethrough_type | |├ (P) text_strikethrough_color | |├ (P) text_effect_type | |├ (P) text_outline_color | |├ (P) text_shadow_direction | |├ (P) text_shadow_color | |├ (P) text_glow_color | |├ (P) text_secondary_glow_color | |├ (P) text_gfx_filter | |├ (P) text_all_styles | |├ (M) text_style_apply
|Open||None||T7510 evaluate stabilization potential of efl.ui classes and dependencies|
|Resolved||ali.alzyod||T7941 enum Efl.Text_Style_Strikethrough_Type|
|Resolved||None||T7942 enum Efl.Text_Style_Background_Type|
|Resolved||None||T7943 enum Efl.Text_Style_Effect_Type|
|Resolved||None||T7944 enum Efl.Text_Style_Shadow_Direction|
|Resolved||None||T7945 enum Efl.Text_Style_Underline_Type|
The proposed rework:
interface Efl2.Text.Style.Properties ├ (P) foreground_color ├ (P) background_type ├ (P) background_color ├ (P) underline_type ├ (P) underline_color ├ (P) underline_height ├ (P) underline_dashed_color ├ (P) underline_dashed_width ├ (P) underline_dashed_gap ├ (P) underline2_color ├ (P) strikethrough_type ├ (P) strikethrough_color ├ (P) effect_type ├ (P) outline_color ├ (P) shadow_direction ├ (P) shadow_color ├ (P) glow_color ├ (P) glow2_color ├ (P) gfx_filter ├ (P) halign_auto_type ├ (P) halign ├ (P) valign ├ (P) line_spacing ├ (P) line_spacing_factor ├ (P) line_height ├ (P) line_height_factor ├ (P) tab_width
├ (P) underline2_color ├ (P) glow2_color
These seem like they should be renamed to something clearer.
The changes are:
- rename the color properties (good imo)
- add these properties
├ (P) halign_auto_type
I think the idea here is that you have the option of 1) disabling it 2) respecting the internal property value from being set in API 3) autodetecting it based on locale. I'm not sure why 3 exists, however, since it seems like 2 should be applied based on the locale? Confusing.
├ (P) halign ├ (P) valign
These properties seem duplicated around a few times in the text APIs; I'm not sure I see a need for this beyond using the content_align property at a higher level unless I'm missing something?
├ (P) line_spacing
This is pixels?
├ (P) line_spacing_factor ├ (P) line_height
This is pixels?
├ (P) line_height_factor ├ (P) tab_width
Should probably be uint type?