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

FrameworkElement default Measure/Arrange override imeplementation #1554

Closed
3 of 5 tasks
dr1rrb opened this issue Sep 17, 2019 · 0 comments · Fixed by #13839
Closed
3 of 5 tasks

FrameworkElement default Measure/Arrange override imeplementation #1554

dr1rrb opened this issue Sep 17, 2019 · 0 comments · Fixed by #13839
Labels
difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/bug Something isn't working platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform platform/wasm 🌐 Categorizes an issue or PR as relevant to the WebAssembly platform project/layout 🧱 Categorizes an issue or PR as relevant to layouting and containers (Measure/Arrange, Collections,..)

Comments

@dr1rrb
Copy link
Member

dr1rrb commented Sep 17, 2019

Current behavior

If you create a Panel which arrange all its items and then invoke base.ArrangeOverride(finalSize) the first item is re-arranged stretched, while on windows it seems to do nothings.

Expected behavior

The arranged items are not re-arranged ...

BUT

It seems that on UWP you can invoke the base to arrange items (for instance if you only alter the finalSize and call the base, it seems that all items are arranged properly)

How to reproduce it (as minimally and precisely as possible)

Cf. the (private) issue attached in the conversation thread below

Environment

Nuget Package: Uno.UI
Package Version(s): 1.46
Affected platform(s):

  • iOS
  • Android
  • WebAssembly
  • Windows
  • Build tasks

Visual Studio: irrelevant
Relevant plugins: none

See #97

@dr1rrb dr1rrb added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform platform/wasm 🌐 Categorizes an issue or PR as relevant to the WebAssembly platform labels Sep 17, 2019
@ghuntley ghuntley removed the triage/untriaged Indicates an issue requires triaging or verification label Sep 24, 2019
@francoistanguay francoistanguay added this to the 3.1 milestone Aug 29, 2020
@carldebilly carldebilly modified the milestones: 3.1, HighPriority, HotFixes Aug 31, 2020
@carldebilly carldebilly modified the milestones: 3.1, 3.2 Sep 14, 2020
@agneszitte agneszitte added the project/layout 🧱 Categorizes an issue or PR as relevant to layouting and containers (Measure/Arrange, Collections,..) label Sep 21, 2020
@jeromelaban jeromelaban removed this from the 3.2 milestone Oct 19, 2020
@jeromelaban jeromelaban added the difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. label Feb 15, 2021
@carldebilly carldebilly added this to the 3.6 milestone Feb 16, 2021
@francoistanguay francoistanguay modified the milestones: 3.6, 3.7 Mar 17, 2021
@carldebilly carldebilly removed this from the 3.7 milestone Apr 7, 2021
@MartinZikmund MartinZikmund added difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI and removed difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels May 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/bug Something isn't working platform/android 🤖 Categorizes an issue or PR as relevant to the Android platform platform/ios 🍎 Categorizes an issue or PR as relevant to the iOS platform platform/wasm 🌐 Categorizes an issue or PR as relevant to the WebAssembly platform project/layout 🧱 Categorizes an issue or PR as relevant to layouting and containers (Measure/Arrange, Collections,..)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants