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

Solar2D Widgets
#401

Alex…

Thanks for all the great work on the widgets!

And don’t do this if you believe it will cause any regression, but would you look at whether you believe the scrollView should perform callback to it’s event listener during “bounce” and “scrollToPosition” phases as well.   Right now, it only makes the callback in relation to actual “touch” (manual) events.   This improvement will allow us to better keep native objects in-position without resorting to heavy-handed tactics.   Adding “bounce” and “scrollTo” phases would be enough for anyone who’s worked around the prior omission to ignore the new more uniform callbacks.

Much appreciation!

D

#402

Great idea!

#403

Any new on when this might be ?

#404

Soon.

#405

@alex,

Any idea when bug 30464 - scrollView issues: scrollbar jumps, scrollbar cut off at top might get looked at?

Since the issues are also in 2100, I understand they won’t make it in the public build, but they have not been fixed along with the other scrollView issues that were recently addressed, so just wondering when they might get some attention.

Thanks!

#406

object:scrollTo( “bottom” ) seems to scroll to the bottom but place the bottom in the center of the scrollview, not at the bottom of the area as it should. Perhaps there is an anchoring issue, but I can’t find docs for this! Help!

#407

@mimetic I have notice this also but I changed it so I don’t use it. I also thought it might be an anchor issue.

#408

I’m a bit surprised, that the new public build is already released. Does this mean that all mentioned widget bugs are fixed as announced for the upcoming public build?

#409

@sunmills: All the included fixes are here: https://developer.coronalabs.com/content/corona-sdk-release-notes-build-2014-2189.

#410

@alexf now that the public build is released could you please update the github repository for widgets. I really need to merge my modifications with the new source before moving to the new build.

Thank you

#411

@primoz.cerar: It’s done, i was just merging in when you wrote the post.

alex

#412

Great news. Sorry to annoy you about this but i really need it before I move to the new build.

Thank you.

#413

You’re not annoying at all.

With pleasure!

alex

#414

Excellent news, even! Updated 10 minutes ago!

https://github.com/coronalabs/framework-widget

#415

@alexf

Thanks for clarify, I got something wrong. Looking forward to the next batch of fixes!

#416

Thanks very much for the fixes Alex…

has anyone patched “newPickerWheel” to scale properly on 640 x 960??  If not, does anyone have ideas on how to do it?  That’s something I’ll need done in the next month or so and would love it if it’s already been accomplished.

Also, many months ago Rob made (what I thought was) an excellent suggestion about us standardizing on 1800x1200 content-area in config.lua.  It’s a nice clean, highly granular and easily divisible set of dimensions.  If that is to be the official, recommended “best practice”, then is there any plan to make the widgets either scale or default to those dimensions.

#417

oh, Alex, your link of new fixes has a period at the end…making it broken…may want to fix that…

#418

anybody else running into this with the newScrollView in v2189

attempt to perform arithmetic on field ‘_oldAnchorX’ (a nil value)

    ?: in function ‘_calculatePosition’

#419

I had that when I included some widget sources in a subfolder or under a different file name. Basicaly that happens when you require your own widget.lua version that has a different name say mywidget.lua or is in a subfolder, however the widgets themselves (say scroll view) also require widgets.lua (this will be the built in one) in their code. If this files are not the same one then you get the error you mentioned. To fix it either move your widget.lua to the root project dir or you will have to include all the widget files that you use and fix the require statements in them. Scroll view for example would need widget.lua, widget_scrollview.lua and widget_momentumscrolling.lua.

#420

Tick tock tick tock… One more week to go before the anniversary of Widgets 2.0 release…

It was a refreshing sight to see some much needed fixes to the widget.newSwitch about two weeks ago but since then again all trails went cold. More bugs are being discovered daily while none are being fixed. Perhaps the team is hard at work to release a another big batch of fixes and what a lovely surprise this would be… Having said that, I always think smaller fixes coming out more often is the way to go in dealing with this beast!!!

Please Corona Labs. Make it happen. Lets all have a nice one year anniversary celebration for the widgets… Thank you.