-
Notifications
You must be signed in to change notification settings - Fork 24
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
Fixed Bugs and Made Changes #13
Comments
Tried your fix - worked like a charm! Thank you! |
Awesome, thanks. |
Hi, I've tried master (as these changes aren't versioned yet) and it works fine when I develop and reload the app, but not on when I launch the app for the first time. I can't really figure out what the issue is, it appears that However, googling around, it seems that |
Hi again, I did additional tests, and I believe that All I did to test is to implement a viewcontroller, and use it in my AppDelegate:
Unfortunately I have no idea how to send an event to js, here I need your help :) |
Last comment for today, promised. I made it work with a hack: I created the controller, sent a notification, and used this module to listen to my own notification instead of I asked on SO, if I can find a better/cleaner solution, I'll post a PR: |
Merged. #16 |
Hey, I know there is some official means of doing this but I'm not familiar with git really...
Anyway I made some changes I think are pretty good including the bug fix mentioned in previous
I now include the actual device orientation in the dictionary. I also fixed the issue with sending the wrong width / height (it was flipped around).
Then I receive the orientation in the event receiver and parse it. I also send the new data in the handler.
I parse the orientation to return easier to work with object:
And now my handler receives:
NEW ORIENTATION DISCOVERED!
index.ios.js:22 Height: 716
index.ios.js:23 Width: 414
index.ios.js:24 Orientation:
index.ios.js:25 Object {current: "portrait", idle: true, facing: "up"}
The text was updated successfully, but these errors were encountered: