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

An rare issue with NGUI, Unity 2018 and mobiles. #54

Open
NDark opened this issue Aug 7, 2021 · 0 comments
Open

An rare issue with NGUI, Unity 2018 and mobiles. #54

NDark opened this issue Aug 7, 2021 · 0 comments

Comments

@NDark
Copy link

NDark commented Aug 7, 2021

There is an rare-observed issue as NGUI and Log Viewer co-existing in Unity 2018 on mobile platforms. Because rare articles encountered and talked about this, I think it is worthy to mention, in case others face the same problem.

Description:

As coexisting with NGUI, Log Viewer in Unity 2017 works fine on my project but when I tried to upgraded to Unity 2018 Log Viewer mal-functioned only in tapping buttons and tapping log items on mobile platforms (iOS and android).

Solution:

Disable auto hide cursor of NGUI UICamera at first scene solved the problem.

Test environment:

  • Log Viewer versions : before 1.7
  • Unity 2017 mobile (android/ios/editor/webgl): all fines.
  • Unity 2018 editor/webgl: fine, android/ios: failed to tapping on navigation buttons and log items.
  • Upgrading Log Viewer to version 1.8 didn't solve this issue.
  • Scrolling navigation buttons(horizontal) and scrolling log items(vertical) are fine always. But unable to tap close button to close Log Viewer.
  • First scene with Log viewer reporter, a NGUI root, UICamera(UIevent) and panels which not destroyed between scenes; Other scenes with their own NGUI root, UICamera, and other NGUI objects.
  • A article attracts my attention, so auto hide cursor setting in UICamera of NGUI did solve this issue.
  • Even though the UICamera(s) in other scenes checked the auto-hide-cursor by default, but only un-ckecking auto-hide-cursor of the UICamera in the first scene solved the issue. (No need to un-check the setting in all the scenes)
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

1 participant