Another Pickerwheel thread...

Hello All,

I am working on a new app and I need two pickerwheels of custom width. I know the docs they dont support scaling, but come on, there has to be reasonable way to resize the width of these things. I have included a screenshot of my issue. I gave the frame of the pickerwheel a custom width but I cant place it over the column…

        local columnData = 

        { 

           --prefix column

           { 

              align = “right”,

              labels = prefixes,

              width = 45

           }

        }

        local prefixPickerWheel = widget.newPickerWheel{

           left = 50,

           top = 30,

           overlayFrameWidth = 75,

           backgroundWidth = 75,

           width = 75,

           fontSize = 24,

           columns = columnData

        }

I can’t believe such a simple control is driving me this nuts, I am very close to writing it native iOS

Joseph

Hello,

Did you create the mask image? If so, it’s not specified in your code. Also, masks need to adhere to various rules described in the masking guide (http://docs.coronalabs.com/guide/media/imageMask/index.html). In the upcoming Graphics 2.0 engine, dynamic “masks” (containers) will circumvent this task, but for now, you need to create and declare the mask file correctly… you can’t just arbitrarily set the width and height in the overall widget setup.

Also, the width of the columns is what dictates the overall width of the unit, and you can’t change the size of the picker wheel after you initially create it.

Hope this helps,

Brent Sorrentino

When is Graphics 2.0 expected? 

If the column width determines the width of the whole thing, then why if I have one column of width 45 does it stretch the full 320 anyway?

Graphics 2.0 is currently in beta testing:

http://www.coronalabs.com/blog/2013/08/07/corona-update-graphics-2-0/

As for the other issues, I believe the picker wheel is undergoing some improvements and modifications this week or next. I’ll also be writing a tutorial about how to “skin” this widget (and some others) when these mods are worked in.

Take care,

Brent

I had some similar problem too. After some experimenting, I did this way :

columnData = {

{

    align = “left”,

    width = 145,

    startIndex = pickerStartIndex[1],

    labels = data[1],

                    

},

{

    align = “right”,

    width = 145,

    startIndex = pickerStartIndex[2],

    labels = data[2],

                    

}},

Hello,

Did you create the mask image? If so, it’s not specified in your code. Also, masks need to adhere to various rules described in the masking guide (http://docs.coronalabs.com/guide/media/imageMask/index.html). In the upcoming Graphics 2.0 engine, dynamic “masks” (containers) will circumvent this task, but for now, you need to create and declare the mask file correctly… you can’t just arbitrarily set the width and height in the overall widget setup.

Also, the width of the columns is what dictates the overall width of the unit, and you can’t change the size of the picker wheel after you initially create it.

Hope this helps,

Brent Sorrentino

When is Graphics 2.0 expected? 

If the column width determines the width of the whole thing, then why if I have one column of width 45 does it stretch the full 320 anyway?

Graphics 2.0 is currently in beta testing:

http://www.coronalabs.com/blog/2013/08/07/corona-update-graphics-2-0/

As for the other issues, I believe the picker wheel is undergoing some improvements and modifications this week or next. I’ll also be writing a tutorial about how to “skin” this widget (and some others) when these mods are worked in.

Take care,

Brent

I had some similar problem too. After some experimenting, I did this way :

columnData = {

{

    align = “left”,

    width = 145,

    startIndex = pickerStartIndex[1],

    labels = data[1],

                    

},

{

    align = “right”,

    width = 145,

    startIndex = pickerStartIndex[2],

    labels = data[2],

                    

}},