cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
rwittels
Responsive Resident
Responsive Resident

App.Width is not working

Hi. This seems to be a recent issue with Power Apps. With Scale to fit off, App.Width is giving me values which are double my browser size. My screen is 1920 width but when my app runs in full screen, it gives me 3839 as the App.Width. If I resize my browser's width, the value is always double. This is affecting icon positions where I am using App.Width - Self.Width. I haven't had this issue in the past so this must be a recent problem. Also, if I set an item's width to something like this: If(App.Width<=1080,App.Width,1080) so that my app never exceeds 1080 in width, it makes my app 540 in width on my 1920 screen. I have checked this in both Firefox and Chrome with zoom set to 100%.

1 ACCEPTED SOLUTION

Accepted Solutions

Oh, haha glad you got it working. Though, when I said App.Height/Width formulas I did not mean precisely App.Height/App.Width etc, was just typing lazy and saying all my location and size formulas reference app.width & app.height and used a / instead of & app. to shorten it. But the formula you ended up with can also be rewritten as 

 

If(App.Width>App.Height,App.Width,App.Width*0.5625)

 

to look a little more normal

 

Here are the settings I use personally to keep everything adaptive

 

settings1.PNGClick SCREEN name, and above be sure Width and Height are Set to App.Width & App.HeightClick SCREEN name, and above be sure Width and Height are Set to App.Width & App.HeightControls that are full screen width are App.Width for widthControls that are full screen width are App.Width for widthAs you can see even when switching to a wide screen this control adaptsAs you can see even when switching to a wide screen this control adapts

So as you can see above, I have changed the Width & Height Settigns for EACH SCREEN to App.Width & App.Height respectively. The default is Max(App.Width, App.DesignWidth) which can be a problem because say you DESIGN the app in a 1024 wide canvas then drop down into a device that is 960, well its going to take the largest of the two, which is the design width of 1024 and try to make all your controls that size, which will be larger than the 960 you have in the smaller device.

 

So once all your screens are set to App.Width & App.Height as their values then the controls in the screen itself can reference app.height & width properly (if its still set to max main issue is it becomes hard to do things like swipe out of the app) so for example in the image above one control (the light box) is full width in both mobile phoen size, and in browser size because its width is set to app.width. You can also do things like App.Width * .5 for one half screen width or .9 for 90% etc. 

 

then centering controls liek app.width/2-self.width/2

 

once you get the hang of it this is the best way to design responsive apps really

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

View solution in original post

6 REPLIES 6

Have you checked the Screen itself. If you worked on the screen at all before switching the layout, it is possible clicking on it then looking for width will show you something like Max(App.DesignWidth,App.Width) which will often give you some weird returns.

 

I use app.width/height formulas in all my apps and have experienced no issues lately, so think it may just be a setting somewhere we need to get set right on your app

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

Thank you for responding. I have been building Power Apps on the same laptop for 2 years. I have never noticed this issue. I created a blank canvas app and added the below labels. Width exceeds my screen width. What else can I check?

 

Windows res:

rwittels_0-1660814802601.png

 

Browser zoom:

rwittels_1-1660814841312.png

 

App defaults:

rwittels_4-1660815101656.png

 

App display settings:

rwittels_5-1660815151779.png

 

Power App Studio:

rwittels_9-1660815693993.png

 

App running in browser:

rwittels_8-1660815651339.png

 

 

 

 

rwittels
Responsive Resident
Responsive Resident

@TheRobRush- using your suggestion of App.Width/Height, this workaround works for me:

If(App.Width/App.Height<1,App.Width,App.Width*0.5625)

 

I still think that there is something very wrong with the way Power Apps detects App.Width because if I set the width of the blue rectangle to App.Width/2 it gives me a rectangle of 960 width which is correct, but if I set it to 1080, as shown above, it gives me a rectangle of 541.

Oh, haha glad you got it working. Though, when I said App.Height/Width formulas I did not mean precisely App.Height/App.Width etc, was just typing lazy and saying all my location and size formulas reference app.width & app.height and used a / instead of & app. to shorten it. But the formula you ended up with can also be rewritten as 

 

If(App.Width>App.Height,App.Width,App.Width*0.5625)

 

to look a little more normal

 

Here are the settings I use personally to keep everything adaptive

 

settings1.PNGClick SCREEN name, and above be sure Width and Height are Set to App.Width & App.HeightClick SCREEN name, and above be sure Width and Height are Set to App.Width & App.HeightControls that are full screen width are App.Width for widthControls that are full screen width are App.Width for widthAs you can see even when switching to a wide screen this control adaptsAs you can see even when switching to a wide screen this control adapts

So as you can see above, I have changed the Width & Height Settigns for EACH SCREEN to App.Width & App.Height respectively. The default is Max(App.Width, App.DesignWidth) which can be a problem because say you DESIGN the app in a 1024 wide canvas then drop down into a device that is 960, well its going to take the largest of the two, which is the design width of 1024 and try to make all your controls that size, which will be larger than the 960 you have in the smaller device.

 

So once all your screens are set to App.Width & App.Height as their values then the controls in the screen itself can reference app.height & width properly (if its still set to max main issue is it becomes hard to do things like swipe out of the app) so for example in the image above one control (the light box) is full width in both mobile phoen size, and in browser size because its width is set to app.width. You can also do things like App.Width * .5 for one half screen width or .9 for 90% etc. 

 

then centering controls liek app.width/2-self.width/2

 

once you get the hang of it this is the best way to design responsive apps really

_____________________________________________________________________________________
Like my answer? - Hit that Thumbs Up. Resolved the Issue? - Hit Accept as Solution.
This helps others find solutions to future issues!

Thank you. This has been a very useful conversation and I appreciate your assistance.
I am still super confused as to why App.Width and App.Height give me values greater than my screen resolution.

PASpecialist
Frequent Visitor

Hi all,

 

Facing a challenge that seems to resonate with discussions here. About 1.5 years ago, I developed a Canvas App optimized for mobile but scalable to tablets and desktops in portrait mode, with "Scale to fit" off. All controls, including text inputs and buttons, were designed with relative positions and sizes for a responsive UI, using significantly large font sizes (like 30) for mobile readability, which worked well until I integrated a Rich Text Editor (RTE).

The RTE controls appeared very small compared to other elements. Despite adjusting other controls' sizes for a coherent UI and previously querying this forum for a way to resize RTE controls, I haven't found a satisfactory solution. Interestingly, testing with two identical screens in both my original app and a newly created app revealed that new apps might handle App.Width calculations differently, possibly addressing the RTE size issue.

How can we apply these updated calculations or any other method to adjust the RTE control sizes in existing apps? Any workarounds or insights would be greatly appreciated.

 

 

Additionally, I've included below screencaptures that showcase the issue, specifically mimicking the appearance on an Apple iPad 10.2". These visuals should help in understanding the scale of the RTE control size discrepancy compared to other UI elements. Looking forward to any guidance on how to address this within the existing app framework.

PASpecialist_0-1708777151238.png Existing App: App.Height = 2160

PASpecialist_1-1708777170277.pngNew App.  App.Height = 1080

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (739)