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

[TIMOB-12218] Adding test case for significanttimechange event #88

Closed

Conversation

srahim
Copy link
Contributor

@srahim srahim commented Feb 13, 2013

To be tested along with TIMOB PR

GO TO PLATFORM > APPLICATION EVENTS
Background the app.
Change the time zone.(Settings > General > Date & Time > timezone)
Resume the app. You should see the Label change and an alert being fired.

Titanium.App.addEventListener('significanttimechange',function(e)
{
Ti.API.info("Time Change Event Received !! ");
paused = true;
Copy link
Contributor

Choose a reason for hiding this comment

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

why is this set to true? The event can be received when the app is in foreground.

@vishalduggal
Copy link
Contributor

Code reviewed. One minor point. Otherwise looks good.

@vishalduggal
Copy link
Contributor

FR also failed. When the screen first loads up, the two text labels overlap. Perhaps wrap them in a view with a vertical layout and add the view to the window.

@vishalduggal
Copy link
Contributor

Noticed that on the simulator, the event is fired multiple times. Remove the alert because it is annoying. But the good news, I actually got the notification

@srahim
Copy link
Contributor Author

srahim commented Feb 13, 2013

Sorry had some code from the copied over section. Cleaned up the code. Ready for review.

@srahim
Copy link
Contributor Author

srahim commented Feb 14, 2013

Closing out PR as it is picking up older commits. Will make a new PR .

@srahim srahim closed this Feb 14, 2013
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.

None yet

3 participants