AliSherKashif / codenameone

Automatically exported from code.google.com/p/codenameone
0 stars 0 forks source link

Display blank area in Picker when popup in iPhone6 Plus #1330

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create new project with a new Form.
2. Overrides beforeForm and add the Picker in code.
        Picker picker = new Picker();
        picker.setType(Display.PICKER_TYPE_TIME);
        picker.setShowMeridiem(true);

        f.addComponent(picker);
3. Send iOS build and run.

What is the expected output? What do you see instead?
- Expected to have the full width Picker, and the Picker area is accessible.
- However the Picker shows some blank area, which is not accessible.
It happens to both Portrait and Landscape. Landscape gives a larger blank area 
than Portrait.

What version of the product are you using? On what operating system?
iPhone6 Plus, iOS 8.1
No problem with iPhone4S, iOS 8.1

Please provide any additional information below.
It works in previous builds. However I am not sure which version because i 
don't check it regularly.

Original issue reported on code.google.com by jensanth...@gmail.com on 3 Feb 2015 at 1:47

Attachments:

GoogleCodeExporter commented 9 years ago
Assigning to Steve. There are also reports that iOS 7.1 fails when pressing OK, 
can you install the simulator for 7.1 and check that too?

Thanks.

Original comment by shai.almog on 3 Feb 2015 at 6:19

GoogleCodeExporter commented 9 years ago
Fixed.
https://code.google.com/p/codenameone/source/detail?r=2076

Original comment by steve.ha...@codenameone.com on 3 Feb 2015 at 7:27

GoogleCodeExporter commented 9 years ago
Just sent another build but the fix is not ready yet.

Original comment by jensanth...@gmail.com on 4 Feb 2015 at 3:13

GoogleCodeExporter commented 9 years ago
It will be on the server in the next update.  

Original comment by st...@weblite.ca on 4 Feb 2015 at 4:08

GoogleCodeExporter commented 9 years ago
This should now have been fixed for a while.  I can no longer reproduce this 
issue.  I have attached the test case that I am using.  If you are having this 
problem, please try out this test case, and see if you still experience the 
same behaviour.  If not, can you modify the test case to produce the problem 
and repost it?

Original comment by st...@weblite.ca on 16 Feb 2015 at 3:48

Attachments: