So I updated to latest build where iOS7 theme is set for widgets as a default and noticed the blue color of widget.newSegmentedControl. And from what I can see in the documentation you can change this colour? can you please add the option to change colors in segmented controls. Because I do my own graphics there and the blue color is just not right for that.
Can you go to http://feedback.coronalabs.com and add this as a feature request? I’ll also ping engineering on it, but this would be a nice to have.
I totally agree on this one, the bright blue is indeed too off. I couldn’t find a feature request for it so I created one. Should be fairly simple.
“You can have any colour as long as it’s black.”
Henry Ford
Glad we came a long way since the Model T days… I agree this should not require a feature request and should be offered by default out of the box.
Hopefully we can see this in the next daily build?
Something as simple as: “fillColor” and “textColor” that takes an RGB table?
I hope they will go the setFillColor() route too, but it’s pretty unrealistic to expect this in the next daily build for several reasons including asking for it over the weekend, the complexity of actually adding this support and other higher priority engineering tasks currently going on.
The more votes it gets on feedback the higher it will get pushed up the list.
Well, that’s quite understandable. I got a bit too excited as it’s my last draw back for releasing and I didn’t want to re-invent the wheel with my own custom segmentedControl.
However, I do hope it gets picked up fast, because logically speaking, since we’re all building our own applications with our own themes, setting its colour should have been like setting the text colour or any object colour for that matter.
So yeah, soon I hope.
Can you go to http://feedback.coronalabs.com and add this as a feature request? I’ll also ping engineering on it, but this would be a nice to have.
I totally agree on this one, the bright blue is indeed too off. I couldn’t find a feature request for it so I created one. Should be fairly simple.
“You can have any colour as long as it’s black.”
Henry Ford
Glad we came a long way since the Model T days… I agree this should not require a feature request and should be offered by default out of the box.
Hopefully we can see this in the next daily build?
Something as simple as: “fillColor” and “textColor” that takes an RGB table?
I hope they will go the setFillColor() route too, but it’s pretty unrealistic to expect this in the next daily build for several reasons including asking for it over the weekend, the complexity of actually adding this support and other higher priority engineering tasks currently going on.
The more votes it gets on feedback the higher it will get pushed up the list.
Well, that’s quite understandable. I got a bit too excited as it’s my last draw back for releasing and I didn’t want to re-invent the wheel with my own custom segmentedControl.
However, I do hope it gets picked up fast, because logically speaking, since we’re all building our own applications with our own themes, setting its colour should have been like setting the text colour or any object colour for that matter.
So yeah, soon I hope.
Bringing back this thread since the issue has not been addressed as of yet. While it is not possible to color the segmentedControl widget it is possible to apply an alternative theme to it. The current blue frames all come from the theme supplied with the widget. I believe Brent has a long overdue tutorial promise on how to do exactly this. Customizing visuals of widgets via alternate themes.
Brent any idea when we can have this tutorial? Thanks much!!!
I’m waiting for too… 
As soon as I can get past other pressing matters. 
I know everybody is waiting on this…
Brent
Brent,
This is really unfair.
The Particle Designer support was introduced couple days ago and your tutorial followed it just the next day. This skinning tutorial has been promised for over 6 months for a product (widgets 2.0) that was released over a year ago. Perhaps its not as sexy as the brand new stuff being introduced but it is bread & butter for some of us who try to eek a living out it. So please don’t tell us other things are more pressing or urgent. There has to be an embarassment factor related to how long we have been made to wait and things like this should get automatically bumped up to the top of the queue.
Thank you.
Kerem
My 2¢ on this. I don’t believe Brent personally is to blame for the lack of a skinning tutorial, nor anyone in particular. IIRC there are a few outstanding bugs in regards to skinning with the widget library and if that is still the case, then it’s fair to wait before publishing a tutorial that would bring more questions than it answered.
For now, I believe the best way to learn about skinning is to grab the github version of the widget library and open up the theme files. It has information about the properties you need, along with the image sizes it uses by default. I know thats not as good as a tutorial, but it should suffice for now as a guide of sorts.
I admire your enthusiasm Karem and this post isn’t a criticism of you at all, just my thoughts on this. We all want Corona to be the best it can be, of course.
I fully agree. My post above was not meant to be a personal attack and apologies if it reads that way. I’m just very very frustrated at how business app development in general and consequently the widgets are always the second fiddle.
“My post above was not meant to be a personal attack and apologies if it reads that way.”
Hi Kerem,
Back in the day when paper mail was a common mean of communication, a wise person once said, before you mail an angry letter, you should draft it, set it aside, and revisit it later or the next morning. Then if you still think its contents are justified, send it, and you won’t need to apologize or clarify anything within.
Also, remember that your own personal features/needs/priorities do not necessarily represent those of the entire developer community. You may not think that Particle Designer is of any worth, but others clearly feel otherwise. That being said, I’m not dismissing the need for a suite of widgets that are bug free and completely customizable… in fact, internally I push for this frequently and adamantly, so I’m actually on your side. However, other priorities constantly surface and I have to balance these among many other things. In addition, as Gremlin pointed out, there were other factors (bugs) that prevented this from happening earlier, and there may still be some that hold up the presentation of certain widget skinning features. Next week might present a window for me to explore this, but I cannot promise that.
Brent