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

Paul/fix exchange scenes #4739

Merged
merged 6 commits into from
Jan 23, 2024
Merged

Paul/fix exchange scenes #4739

merged 6 commits into from
Jan 23, 2024

Conversation

paullinator
Copy link
Member

@paullinator paullinator commented Jan 20, 2024

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

@paullinator
Copy link
Member Author

Screenshot 2024-01-19 at 20 53 17 Screenshot 2024-01-19 at 20 53 57 Screenshot 2024-01-19 at 21 59 34 Screenshot 2024-01-19 at 20 54 40

@paullinator paullinator force-pushed the paul/fixExchangeScenes branch 3 times, most recently from 85c0699 to 88c4326 Compare January 21, 2024 05:26
Copy link
Contributor

@samholmes samholmes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test on iPad sim to make sure the padding is correct during rotated orientations

sceneMargin
/>
{({ insetStyle }) => (
<View style={{ paddingBottom: insetStyle.paddingBottom, width: '100%', height: '100%' }}>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the extra view instead of using the one with styles.container?

Also, why only use paddingBottom from insetStyle? Using all of the rules usually means we're avoiding insets on left/right and even top sides of the device (e.g. for rotated iPad devices)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The extra View covers all the content including the button at the bottom while the inner View is just the text and spinner.

I didn't actually need the insets at all since all the content is centered. Removed.

renderItem={this.renderPlugin}
keyExtractor={(item: GuiPluginRow) => item.pluginId + item.title}
contentContainerStyle={{ ...insetStyle, paddingTop: 0 }}
contentContainerStyle={{ paddingTop: 0 }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove

@paullinator paullinator force-pushed the paul/fixExchangeScenes branch 3 times, most recently from 4e27e11 to bc0b749 Compare January 23, 2024 06:08
@paullinator paullinator force-pushed the paul/fixExchangeScenes branch from bc0b749 to 0dcfcb5 Compare January 23, 2024 21:56
@paullinator
Copy link
Member Author

/rebase

@paullinator paullinator enabled auto-merge January 23, 2024 21:56
@github-actions github-actions bot force-pushed the paul/fixExchangeScenes branch from 0dcfcb5 to f486edc Compare January 23, 2024 21:57
@paullinator paullinator force-pushed the paul/fixExchangeScenes branch from f486edc to f351efc Compare January 23, 2024 21:59
This allows the header to be transparent on scroll. Also just uses less views.
- Add animations
- Fix margin above Next button
- Make Next button primary
- Add animation
- Increase font size
- Decrease long wait time to 10s
- Use the SceneWrapper scrollview
- Add animations
- Reduce slider marginTop
And use the SceneWrapper so content can go under translucent header
@paullinator paullinator force-pushed the paul/fixExchangeScenes branch from f351efc to 46db58a Compare January 23, 2024 23:02
@paullinator paullinator merged commit 47caae1 into develop Jan 23, 2024
2 checks passed
@paullinator paullinator deleted the paul/fixExchangeScenes branch January 23, 2024 23:12
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