@sunmills: that happened in 2158. Is 2159 still exposing the same behavior for you?
alex
#29891 - Switch moves x-location when I scroll in the scroll view.
#29534 - widget.newSwitch missplacement on Android
#28960 - switch widget is displayed wrong in state = true and theme ~= ios7
#29419 - isBounceEnabled in scrollview is shared with all scrollviews.
#29399 - widget switch shifts upon scrolling in scrollView
#29144 - widgets.newSwitch in onOff style moves left & right on x axis when it is programmatically changed with obj:setState()
#30007 - scrollview problems in compatibility mode.
alex
fixed, thanks!
The code you posted in 29144 looks fine in 2159 here, in both compatibility and non-compatibility.
Anything in the config files? The code you posted does not contain any…
Alex
Can confirm the switch is solid as a rock now. No more wiggling. I had a code mixup earlier this morning and thought it was still moving. Thanks Alex. Great work.
We’re experiencing some issues with the scroll view widget with compatibility mode using build 2161.
Objects being inserted into the scroll view seem to get incorrectly positioned. We also seem to get some strange behaviour when attempting to scroll. Initially nothing is displayed, then scrolling brings the inserted object into view. If we then scroll above the limit in the “up” direction, the list will re-position to the middle instead of the top, which doesn’t seem right.
This is the very simple code we have tried this with:
[lua]
local width = 300
local scroller = AppInfo.widget.newScrollView
{
left = 10,
top = 100,
width = width,
height = 300,
bottomPadding = 0,
scrollWidth = width,
scrollHeight = 300,
hideScrollBar = true,
horizontalScrollDisabled = true,
verticalScrollDisabled = false,
}
local rect = display.newRect(0,0,width,40)
rect:setFillColor( 255,0,0 )
scroller:insert(rect)
rect:setReferencePoint(display.TopLeftReferencePoint)
rect.x = 0
rect.y = 0
[/lua]
Hey timjonrichardson,
We’re aware of the issues in compatibility mode and working on them. Nevertheless, please take the time to file a bug with this.
Thanks,
alex
Here’s another bug to add to the list of open Widget 2.0 bugs:
“Restoring deleted ScrollView feature: endedScroll event”
http://forums.coronalabs.com/topic/43778-restoring-deleted-scrollview-feature-endedscroll-event/
Thanks for adding to the spreadsheet.
Alex -
Any idea when the next free build with some of these fixes will be available? You fixed a bug I opened a couple months ago, yet the free download is still at rev from mid-Dec:
Build 2013.2100
Sorry, I realize this is slightly off topic, just really frustrated as the last build is almost 4 months old now…
We are working to finalize the next public build now. We are trying to squeeze in a couple of last fixes, make sure we didn’t break anything that was working in 2100. I can’t give you a date, other than soon.
Rob
as primoz.cerar mentioned ^
I have some long requested fixes in the 2189 fix list. Yet to test them but this is great news! Thanks for rolling out these bug fixes. Much appreciated.
The scrollview has improved a bit in 2014.2189.
But sometimes the scrollview content jumps when I start scrolling down. Like it’s magnetically snapped to the top, moves a bit, jumps back to zero and then makes a big jump and suddenly scrolls. It’s the same vice versa from the bottom.
It’s not as fluid as it was half a year ago. Overall the usability got worse.
Please fix this quickly.
@alexf I can tell you exactly where the problem is. If you need it just give me a shout, I’ll be glad to help.
I also noticed that if the scrollview position is scrolled up (the position is negative). Horizontal scrolling disabled. If you scroll now to a positive value and lift the finger the scrollview moves automatically back to 0 as expected. If you scroll up during this automatic transition (from positiv to zero) the scrollview moves a bit and if the transition would be over it jumpes during the new transition back to zero for a moment. That generates a very unflowing feel.
Hope it become clear what I mean 
@sunmills: I believe you make a clear explanation. We already have a similar report which i’m looking at, i’ll include your observations into the testing.
@primoz.cerar: Always open to communication. PM-ed you.
alex