List of open Widget 2.0 bugs & promised features...

Solar2D Widgets
#121

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. :slight_smile: 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

#122

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! :slight_smile: 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

#123

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   :slight_smile:

#124

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

#125

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

#126

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

#127

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

#128

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

#129

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 !

#130

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.

#131

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

#132

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. 

#133

@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

#134

Super. Thanks much for your hard work and this update. Most appreciated. 

#135

He didn’t mean it in the sense of go and fix it yourself. But Corona doesn’t offer jour bugfixing and if the bug is holding you back and you can’t afford to wait, Ford would advice you to change your own tires as well.

Edit: Forgot to add the reason I came to this thread… I’m having the same issue as people earlier in this thread. If I’ve got a list of multiple rows and I delete the first row in the tableView, it will animate the remaining rows weirdly, pushing the next coming row up perfectly but not the ones following it.

Also is there a way to disable the animation altogether?

#136

Thats exactly what he meant. And its not a case of changing the tyres. 

And I said nothing about changing tyres ! 

#137

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

#138

Fine. Ford would tell you to go to a private mechanic to fix your steering wheel if you couldn’t wait.

#139

Ever heard of the Ford SUV tire recall? Trust me, in these litigious times no company can afford to sell something broken and then tell you to go fix it yourself. Thankfully nothing we do with the widgets lead to such fatal outcomes but still, what is broken needs to be fixed.

I am thankful to Corona Labs for continued efforts to improve this situation but also can’t help but get frustrated in how long it has taken. IMHO, visibility leads to awareness and focus. So best you can do is to add your bugs to the spreadsheet and edit your lines occasionally when your bugs have been fixed. Lets keep the spreadsheet up to date and hope that it continues to catch attention at Corona Labs. 

Thanks for all the contributions to this thread and the spreadsheet. All the best.

#140

And the tumble weed blew past in silence !

Are you still watching this thread Alex ? even if you dont write in it ?