You cannot be serious with that answer ! I can buy wrenches down the shop, but ford dont expect me to make the steering wheel work on a car I have paid for !
Are the widgets really that marginal for corona that you have to fix it during the weekend? Is there no time for widgets during your primary working time? As far as I see, a lot of people are using widgets and waiting for the fixes. So I really don’t understand this practice at all.
In my opinion less, but stable features are much better then more features with a lot of bugs.
I just saw some updates in the spreadsheet indicating that a number of bugs we’ve been waiting on have been fixed and are now being tested etc. Thanks Alex & Danny for hearing us out and sacrificing personal time over the weekend to get some traction. I know that if we get these widgets fixed and make Corona SDK more useable for business apps it will be only thanks to your professionalism and dedication.
I wish Walter, David and rest of Corona Labs leadership team would take notice and make required resource allocation adjustments so we don’t have to have this cyclic issue.
Now lets play ball! Have a good week all.
PS. I hope more people here would use the spreadsheet. As you can see, what is visible eventually gets attention. If you have a bug that you posted in this forum then please take 30 seconds to record it in the spreadsheet linked in the first post. Thanks
Chirp chirp… crickets. Are we on a “management” enforced radio silence now? ;)
I see some bugs were fixed and listed as such in the spreadsheet. Hope we see these in a daily coming out soon and test them. I look forward to receiving the good news and updated widgets library. Thanks for the hard work.
@ksan: wrong.
Yes, there are some fixes in the pipeline. Testing completed and they will go live soon. Some more fixes on the way.
If i don’t write in a thread, it does not mean i don’t watch it.
alex
Super. Thanks much for your hard work and this update. Most appreciated.
Alex, can we please have what you fixed already? You mentioned that testing was completed and yet the daily releases continue to leave us waiting. Can we just have a github update or something like that? Thanks
And the tumble weed blew past in silence !
Are you still watching this thread Alex ? even if you dont write in it ?
Alex, great job on #1260. Some rough edges still as evidenced by some new issues identified by other members but what I saw in the daily build notes was awesome. Copying below for reference & discussion :
Widget fixes in #1260:
(1) Adding the property scrollBarAutoHide to the constructor for tableView and scrollView. Also fixing a bug that went unnoticed where the scrollbar was created multiple times.
(2) Recreate native behaviour when scrolling to a limit and tapping really fast. Also fixes scroll-back bugs. Casenum #26164.
(3) Detecting swipe events on the tableView while in the “moved” phase.
(4) Small fixes to the tableView row rendering. Adding tableView:reloadData() method for re-rendering. No casenum.
(5) Fixes issues when not setting width or height in the scrollView constructor. Casenum #25256.
(6) Fixes the tableView losing touch listener when entering suspend. Casenum #24731.
(7) Fixes the slider widget not propagating the began phase.
(8) Adding inclusion of the local copy of the slider widget.
(9) Scroll direction propagation in the touch event, moved phase. Also fixing the horizontal snapback for scrollviews. Casenum: #24995, #26409.
(10) Removed test for tableView getRowAtIndex for the moment.
Tested #1. It works and looks great! It should be noted that scrollBarAutoHide default state is true so you don’t need to include this in your tableView or scrollView definition. If you wish to disable this ‘default’ behavior then simply include
scrollBarAutoHide = false,
This is great! Thanks!!!
Tested #9. It works great! Now I can detect direction of scroll in my event listener and respond accordingly.
Just updated the spreadsheet with a new sheet to contain the Fixed items. The main page should only contain the open items. Can the bug owners kindly confirm the fixes and mark their entries as such in the spreadsheet? To make it easy for all involved, here is the link to the shared spreadsheet :
docs.google.com/spreadsheet/ccc?key=0AsuRVbWElS3YdGpCN0V3emtmWnlwQmRUOVlpb3RkOGc&usp=sharing
Thank you very much for your support and cooperation!!!
Hi. Just before I raise a bug I thought I’d check here. I’m stacking 3 tableview’s on top of each other on the same scene to simulate a tab control in graphics 2.0. At any one time, only one is visible while the other 2 are hidden. However, only the bottom-most (i.e. first created) tableview receives input events. You can also see a moving phantom scrollbar from the bottom / hidden tableview on the current visible one, even though the visible ones don’t respond to input. This behaviour is also present in graphics 1.0. Ring any bells or should I be doing something different?
Have you tried to do a :toFront() to bring the tableView you want to see to the front of the display hierarchy?
Rob
Thanks for the suggestion Rob. Unfortunately I get the same behaviour. I’ll raise a bug.
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.