Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/policy application issues #1693

Merged
merged 5 commits into from
Feb 5, 2025
Merged

Fix/policy application issues #1693

merged 5 commits into from
Feb 5, 2025

Conversation

merryman
Copy link
Member

Fixes various issues with style policies such as:

  • Incorrect heuristic when to apply due to breakpoint changes.
  • Accidental overriding of own style properties during application.
  • Inefficient application process due to layout feedback loops.

@merryman merryman requested a review from linusha January 30, 2025 15:53
@merryman merryman force-pushed the fix/policy-application-issues branch from 9babbf5 to 9d78442 Compare January 31, 2025 11:36
@linusha linusha self-assigned this Feb 4, 2025
Conflicting properties such as width, height, extent or textString, value and textAndAttributes are prioritized and weeded out during synthesization in order to avoid confusing behavior.
Previously the check would give incorrect results when nested breakpoints where being applied. A nested breakpoint is a breakpoint defined by a master that was *itself* reached by a breakpoint.
…flag

Replaces old and not very well working control flows with a more sophisticated approach to determining sizing behavior of a styled morph within the context of various layouts.
According to the identified sizing behavior, the extent is applied in varying fashions. Also previously accidental re-execution of layouts would happen due to policies applying themselves, which lead to inefficient layout applications overall. This is now prevented with a meta flag.
Previously some layout applications, including text layout, would cause extent, height or width properies in style policies to no longer apply, although not warranted.
@merryman merryman force-pushed the fix/policy-application-issues branch from 9d78442 to d42c366 Compare February 5, 2025 16:11
@linusha linusha merged commit f95de22 into main Feb 5, 2025
4 checks passed
@linusha linusha deleted the fix/policy-application-issues branch February 5, 2025 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants