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

AppBarButton in CommandBar Rendering Issue #1

Closed
utpal-patel opened this issue Oct 19, 2016 · 3 comments
Closed

AppBarButton in CommandBar Rendering Issue #1

utpal-patel opened this issue Oct 19, 2016 · 3 comments

Comments

@utpal-patel
Copy link

Hello,

I have a one project in that AppBarButton not rendered properly so i tried in this one and had same issue here.

screenshot_2

FYI: In Other Project, I have 1 CommandBar in Listview Item Template in that I have 4 AppBarButton. If a List has 4-5 rows and i tried to navigate one page to other and vice versa. I have noticed memory increased as well as CommandBarDefaultLabelPosition.Right in some cases where label position is by default bottom.

I don't know root cause...any help will be appreciated...

@awkoren
Copy link
Contributor

awkoren commented Oct 28, 2016

Thanks for reaching out. Unfortunately, after some investigation it seems like this is an issue with the XAML platform. We've forwarded this info to the team to look in to. In the meantime, the best workaround we're aware of is not to use dynamic overflow in the command bar. We've updated our sample to reflect this.

@utpal-patel
Copy link
Author

@awkoren Thanks for support!!

Please refer attached image. Hope it is same issue which i have posted.

screenshot_23

In 64 bit it wont arise frequent (only one occurrence while fast switching in navigation) but in 32 Bit it occurs too many times.

Is that work around of that as well?

@awkoren
Copy link
Contributor

awkoren commented Nov 28, 2016

Should be, but no way for us to verify from just a screenshot though since we do not have your code.

@awkoren awkoren closed this as completed Nov 28, 2016
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

No branches or pull requests

2 participants