-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Inconsistent title placement on pump configuration screens #974
Labels
Comments
The expected visual design is actually the one with the bolder text. That is the design implemented for setup screens in Loop, but hasn't been applied to pod replacement flow, it looks like. |
Adjusted the issue title |
itsmojo
changed the title
Misplaced title on pump configuration screens when adding a pump
Inconsistent title placement on pump configuration screens
May 28, 2019
Adjusted issue title to match reality |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While trying to track down why sometimes there is a partial blue button at the bottom of the Pod Pairing screen when setting up an Omnipod on a 5s or an SE and other times there is nothing of the blue button showing, I think I was able to identify where the problem starts. Any time a user does an Add Pump and has to go thru the RileyLink Setup screen, the titles that are normally on the top middle will end up being in a large bold test on the 2nd line for this screen and all the subsequent screens until the pump is fully configured. This causes everything on the various pump setup pages to scroll down. When configuring an Omnipod on a 5s/SE, what remains of the blue Pair button on the Pod Pairing screen on the bottom scrolls completely off the screen when the title is misplaced. After the pump is fully configured, the screen titles continue to stay in the top middle for all subsequent Pod configurations until the pump is deleted and an Add Pump with a Rileylink Setup screen is run again.
To Reproduce
Expected behavior
The screen titles should be staying in the top middle and not on the 2nd line. You can see all the Pod setup screens with the title in the top middle by simply ending the current Pod session and then setting up a new Pod by continuing on to the Pod Pairing screen as shown in the following screenshots as the RileyLink Setup screen will not be used again until the pump is deleted.
If you want to see the Pod setup screens with the titles incorrectly placed on the 2nd line, you will need to do Switch from Omnipod Pumps -> Delete Omnipod -> Add Pump to get to the RileyLink Setup screen which seems to be the first one in the sequence with the misplaced title that then affects all the subsequent Pod setup screens. Note that the same incorrect title placement can be seen when setting up a Medtronic pump if the RileyLink Setup screen is visited in the sequence (i.e., switching between Pod types for each simulated run should continue to show the problem each time a Add Pump operation is done. An Omnipod pump with a SE was used for demo purposes as the effect of the incorrect title placement is most noticeable when it completely pushes the Pair button off the screen.
Phone
Loop Version
CGM
Pump
Additional context
This issue was the reason why there was no Pair button seen as reported in https://loop.zulipchat.com/#narrow/stream/144120-omnipod_dev/topic/iPhone.20SE.20Pod.20Pairing.20screen/near/166330440 as the new user was switching from Medtronic to Omnipod on his iPhone SE and had to go thru the RileyLink Setup screen when setting up the new Pump.
Issue #973 could potentially be an example of this problem or perhaps related the more generic issue that the table view rows for errors and progress aren’t set up for auto sizing based on content, and doing so creates problems with the method those views use to add padding to keep the button at the bottom.
The text was updated successfully, but these errors were encountered: