That’s great news. Thanks!
Yup. Thats good. Thanks. I was inquiring about the bulk update / fixes which Alex was working on.
Its been quite a while since the last widget fix release and we have a number of old issues plus the new crop of post-IOS 7 flare-ups. IMHO, widgets are the achilles heel of Corona SDK and they continue to get sidelined the in face of other priorities. At least thats how it feels from this side of the equation. Thanks for doing your best to give us what we need but sometimes we just need more & faster.
Please note this is in no shape or fashion a cheap shot at the great work being done. It is more a reflection on how Corona Labs leadership choices impact us on the ground level.
Thanks much for hearing us out.
Almost another month gone by… Are we going to see a widgets refresh soon? Thanks much for the continued efforts in this area.
I also have to dig deeper for fixing bug Nr 26164. It’s about that the tableView, and scrollView with horizontal scrolling disabled, does not move back if the finger was moved more in x direction as in y direction.
Later I figured out, that small movements in y direction also will cause no return to the origin.
Of course is this no absolute top priority bug, but my release date is approaching and tableViews are such an important part, that I’m not willing to release with this striking blemish.
Thanks for effort with this!
Hi Kerem,
The iOS7 theme is available; have you checked it out yet?
I’ve bumped #26164 to be investigated by the engineers as soon as possible. Thanks for your patience on this.
Brent
That’s great news. Thanks!
Yup. Thats good. Thanks. I was inquiring about the bulk update / fixes which Alex was working on.
Its been quite a while since the last widget fix release and we have a number of old issues plus the new crop of post-IOS 7 flare-ups. IMHO, widgets are the achilles heel of Corona SDK and they continue to get sidelined the in face of other priorities. At least thats how it feels from this side of the equation. Thanks for doing your best to give us what we need but sometimes we just need more & faster.
Please note this is in no shape or fashion a cheap shot at the great work being done. It is more a reflection on how Corona Labs leadership choices impact us on the ground level.
Thanks much for hearing us out.
Almost another month has gone by. Please help us understand why the cumulative fixes are taking so long to come out? Are you trying to get all widgets fixed and G2 compatible in one swoop? Because if thats the case I can both understand the delay and make a decision on waiting or not (more likely not…)… I hope one last round of fixes can be released without going through the G2 hoopla. This sub-forum is a pain to review and I am surprised Corona Labs management is not doing more to make all this noise go away.
Hello Kerem,
Yes, part of the long-awaited “package” is Graphics 2.0 compatible widgets, with the known issues fixed as well. This is more complicated than it may sound, since the widgets have to work with both 2.0 and 1.0, and depending on if the user has V1 Compatibility set or not. This also extends to the usage of containers vs. masks in 2.0 vs. 1.0.
In summary, we are not “ignoring” widgets, and we know you’re frustrated (and have been for some time). I just want to tell you that we’re working on this.
Brent
This is the worst possible decision. G2 will take ages to bring to production and then ages more to make bug free. Meanwhile we have a bug-ridden widget 2.0 implementation that was supposed to be getting fixes and we have all been very patiently waiting. Now to say the fixes will roll out as part of the G2 roll out and G2 compatibility will be part of the widget fixes mean we will surely have to wait longer and longer… I needed something last week as was promised and now I know I won’t be getting anything I can rely on anytime soon.
I have spent most of this year waiting for this or that to be fixed. My Pro subscription is ticking over for nothing while waiting for Corona Labs fixes. This is not right.
Hi Kerem,
I did not state that the widget fixes will wait until G2 was complete and shipped. I meant that they are being adapted to work with G2-related features (which, if I recall, was something you were pleading for quite some time ago, and we are fully aware of its need). So, this is why it’s taking longer than expected.
Regarding your other post, I find it a slight exaggeration to state that “every widget is ridden with bugs”, implying that they are literally non-functional. I just spoke to Alex (during my evening off hours, not working hours) and he confirmed just a few pressing bugs, and a few minor ones. Alex states that he will be addressing most of the remaining bugs this weekend.
Brent
Brent, thank you very much for your kind response. I realize this is your evening rest hours and you really should be doing that and not responding to forum posts. Please understand that I have nothing but utmost appreciation and respect for the work that you, Alex and the rest of CL team does.
I’m not sure what I was pleading for. Been so long its all blending to one another. Auto-masking perhaps? Thats the only thing that G2 will do for widgets as far as I know so perhaps that was it. Anyways, I can only imagine what a large undertaking it must be to bring G2 to the table and then to update the surrounding Corona SDK eco-system to coexist with it and more importantly to make use of it. It’ll all be good one day but the question is how far that one day is from now…
I stand by my assertion in the other post. I can update my spreadsheet if you like but I know this is a waste of time as you already have the same info and more in the bug database. Right now, there is not one widget that is without at least some bugs that we are having to work around or completely sit back and wait for fixes. Do you really need me to list these? Because I will if it will help anyone.
Once again, I appreciate your effort to respond in your free time, Alex’s effort to fix the widgets over the weekend (as you mention above…) but IMHO, this is precisely where the issue lies… It appears to me that widgets continue to be an under-resourced part of Corona SDK. IMHO, Walter and rest of Corona leadership needs to take a long & hard look at where resources are allocated. I recall saying almost the same things earlier in the year and not much has changed since then…
G2, Windows publishing etc are all great for future but if we can’t build apps today using a service we are paying for that is not quite right. Not much more I can say to articulate my problem. Hope this is clear. Thanks for hearing me out.
Hi Kerem,
I hear you, and Alex has various fixes scheduled for the weekend. Also, sorry for sounding abrupt in my previous post… I sometimes get frustrated too and wish that things could happen faster, or sooner, but the reality is that this industry moves quickly and we have to allocate resources when, where, and how we can while maintaining something that resembles a “life”. At least until somebody invents a cloning machine. 
I enjoy the challenge (we all do) and your previous reports did help narrow down the issues. Fortunately, I’ve recently taken some other tasks (documentation-related fixes) off Alex’s plate, so hopefully that frees up his schedule a bit for this.
Take care,
Brent
Hey Brent,
No worries. I too was too stressed over the last couple days with a looming college application deadline for my daughter… Gosh the Common App system is so buggy its not even funny. I guess I got too worked up with their bugs and let it all loose on CL bugs! I’m sorry if I offended anyone around here. My intentions are truly well. I will update the spreadsheet as much as I can but of course if the bug owners did it directly it would be so much more efficient.
Anyways, hope you guys don’t work too much this weekend and manage to get some rest too.
All the best.
Kerem
I also wonder that apparently nobody is primary responsible for the widget library. Some bugs are really major and are reported since months without fixes. And I’m sure most of them could be fixed in a few hours or less.
I can understand that bringing out new features is more attractive, but some customers payed for the features available at the time of purchasing and therefore fixing those bugs should have a very much higher priority in my opinion. At least the widgets are an inherent part of the sdk an no third party stuff.
Corona needs a 100% widget guy
Just a reminder, Widgets are open source. If there is a fix you need (in particular on things that are edge cases), you are more than welcome to download the code from Github and make your own modifications.
https://github.com/coronalabs/framework-widgets
I know it’s not optimal, but if something is holding you back or you need a feature added, it’s all in Lua and available to you.
Rob
Rob,
This remark is really getting old. I don’t want to pay for something and then have to fix it. I also don’t want to fix something which I know will be changing in ways I don’t know about or can control (ie G2 compatibility). And what if I don’t know Lua well enough to attempt these fixes…
Bottomline is that the widgets are part of Corona SDK. Whether a 1% (as per David) or 100% (as per business app developers) it is a part and Corona Labs has an (ethical and legal) obligation to its paying customers to make all reasonable efforts to deliver a working set of code and fix issues on a timely basis when they occur. Can we at least agree on who is accountable here? Thanks and wishing you a good weekend.
Kerem
Hey Ksan.
In your opinion, out of all the bugs listed on the spreadsheet you created, how many are priority 1’s?
Priority 1’s would mean critical fixes.
Cheers
Hi Danny,
Thanks for asking. The list has not been updated and maintained for a while so in all likeliness there are more important isses in the forum and CL bug database. Still, at one glance to the list as it stands now, I can pick the following :
newScrollView event.direction not updated until event.limitReached = true
newSlider no “began” event for slider widget
newTableView the touch handler is dying on the Tableview after the phone has been asleep
newTableView tableview reRender gone
newTableView Deleting a tableview row results in other rows jumping up and down on touching anywhere on tableview.
There are a bunch of other entries regarding deleting tableview rows as well so I think it would be a good idea to tackle the tableView issues along with the reRender capability. A good place to start?
Many thanks for all your hard work.
Regards,
Kerem
For me its the tableview that really needs to be number 1 focus.The issues below have been bouncing around the forums with multiple promises for the last 6 months. Without a proper working tableview, business apps are pretty much dead in the water.
newTableView the touch handler is dying on the Tableview after the phone has been asleep
newTableView tableview reRender gone
newTableView Deleting a tableview row results in other rows jumping up and down on touching anywhere on tableview.
Combine that with the fact that we cant even add rows to a table view with Graphics 2.0
When calling insertRow on a tableView I am getting the error
?:0: attempt to index field ‘_rows’ (a nil value)
message
stack traceback:
?: in function <?:218>
[C]: ?
?: in function ‘_createRow’
?: in function <?:976>
(tail call): ?
And the while thing is unusable