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.

Sign up for GitHub

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

Jump to bottom

Swift3 UI Bug #208

Open
Noodlekim opened this issue Oct 7, 2016 · 2 comments
Open

Swift3 UI Bug #208

Noodlekim opened this issue Oct 7, 2016 · 2 comments

Comments

@Noodlekim
Copy link

We have been updated our source code from Swfft2.x to Swift3.
I found one issue about uibug of CRToast.
Check this screenshot.

Swift2 Swift3
swift2_crtoast swift3_crtoast_uibug
@Noodlekim
Copy link
Author

Noodlekim commented Oct 11, 2016 •
edited
Loading

We’ve solved this issue.
Use setting option like this:

  • Before: [kCRToastNotificationTypeKey : CRToastType.navigationBar.rawValue, …]
  • Modify: [kCRToastNotificationTypeKey : NSNumber(value: CRToastType.navigationBar.rawValue), …]

@atryino
Copy link

atryino commented Nov 30, 2016

Had the same issue after migrating to Swift 3. As well as issues with setting the correct values for:

  • kCRToastAnimationInTypeKey
  • kCRToastAnimationOutTypeKey
  • kCRToastAnimationInDirectionKey
  • kCRToastAnimationOutDirectionKey

Converting these values to NSNumber(value: <value>.rawValue) worked as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Noodlekim @atryino