[TIMOB-6626] iOS: Orientation - Setting orientation with Titanium.UI.LANDSCAPE_LEFT did not set navbar to smaller landscape size
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-12-14T10:55:33.000+0000 |
| Affected Version/s | Release 1.8.0.1 |
| Fix Version/s | Sprint 2011-50, Release 1.8.0.1, Release 2.0.0 |
| Components | iOS |
| Labels | qe-ios121211, regression, verified-1.8.0.1 |
| Reporter | Eric Merriman |
| Assignee | Blain Hamon |
| Created | 2011-12-13T11:06:24.000+0000 |
| Updated | 2012-03-02T11:25:10.000+0000 |
Description
Description:
In KS, on the Phone>Orientation> test, clicking the "Set landscape" button rotates the UI to landscape, but the navBar remains the larger "portrait size" instead of slimming to the smaller "landscape size". This does not occur with 1.7.5. In 1.7.5 the button rotates the UI and the navBar sizes appropriately.
Steps to reproduce:
1) Install KS built with SDK 1.8.0.1
2) Navigate to Phone>Orientation>
3) Click the "Set landscape" button
Result:
UI rotates, but navBar size remains "portrait"
Expected:
UI rotation and navBar resize
Note:
Does not occur with 1.7.5 SDK and KS
Okay, after experimenting, the exact sequence is, while in portrait, press 'Reset Orientation' then 'Set Landscape'
Tested with studio version 1.0.7.201112140358 Ti Mob SDK 1.8.0.1.v20111214093905 OSX Lion iPhone 4 OS 4.3.5 iPad 2 OS 5.0.1 Expected behavior of setting orientation to landscape is shown *Keeping open until testing begins against 1.9.0
The checked-in fix seems to prevent building the application on the simulator for me. Looking at the code, it looks like ignoringRotationToOrientation which was moved from TiWindowProxy was defined in TiViewController.h, but the empty method was never added to TiViewController.m. Perhaps a file was missed on the commit? Adding the method fixes my build problem.
Mike - We are not getting this error internally. You will need to clean your project after switching to a new SDK - there could be a stale object file which contains the old build symbols. If the issue persists, we require a full build log.
Closing as verified fixed against 1.8.0.1