Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Developer
Posts: 136
Registered: ‎01-25-2010
My Device: Z30, Z10, Q10, Dev Alpha B & Bold 9900
My Carrier: Bell
Accepted Solution

DateTimePicker scaling issue

Hi,

 

I'm running into a particular display issue with the DateTimePicker... I've set the DateTimePicker to preferredWidth: Infinity in order to have it fill the entire screen. This works fine when the DateTimePicker is set to the default mode which is DateTimePickerMode.Date.

When ever the other modes are selected, the control does not scale... I've added a code snippet which reproduces the issue noted above... Any suggestions ?

        Container
        {
          leftPadding: 20
          rightPadding: 20
          topPadding: 20
          bottomPadding: 20  
        
          DateTimePicker 
          {
            id: dateTimePicker
            preferredWidth: Infinity
          } 

          DateTimePicker 
          {
            id: dateTimePicker2
            preferredWidth: Infinity
            mode: DateTimePickerMode.Time
          }   

          DateTimePicker 
          {
            id: dateTimePicker3
            preferredWidth: Infinity
            mode: DateTimePickerMode.DateTime
          }   
        }   

 

Developer
Posts: 17,019
Registered: ‎07-29-2008
My Device: Z10 LE, Z30, Passport
My Carrier: O2 Germany

Re: DateTimePicker scaling issue

report in on jira
https://www.blackberry.com/jira/secure/Dashboard.jspa
----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Developer
Posts: 136
Registered: ‎01-25-2010
My Device: Z30, Z10, Q10, Dev Alpha B & Bold 9900
My Carrier: Bell

Re: DateTimePicker scaling issue

[ Edited ]

Did report the issue on jira and it's a know issue and will be fixed in 10.1.x.