I’m also getting black text in scrollviews using 2014.2130 on the simulator. Haven’t tried devices yet, but this is bad enough. 
More precisely, the text renders as solid black rectangles. In some cases, the rectangles disappear and it renders properly when the scrollview is scrolling.
Build 2130 has the black text problem. It’s solved in 2135.
Rob
You guys are awesome thanks!
Have discovered that the scrollview is having trouble with images that have transparency. I got some images to display, but they were “streaked” almost like a strong horizontal blur. You couldn’t see anything but the background color of the image itself. I tried this with a PNG and a JPG.
I know there was a post about this, but am struggling to find it. Just a quick update, Thanks!
I believe people put images with transparency in scrollView’s all the time. What version are you using? BTW: JPG’s don’t have transparency.
Rob
Thank you for the reply. Since JPGs don’t have transparency I tried them to see how they interacted with the Samsung emulators. I only changed some of the images and removed masks to see how it was coming out on the certain devices. It works on other Samsung emulator devices like it should. There are also scrollviews with only text that are working fine. I’ve built it on all of the latest daily builds (except the last 4) and back as far 2100.
The app is alive and well on Nook Tablets, which share similar specs to the device that isn’t working. Is the maxTexture per screen? Or, is it an accumulation of masks and layers through the app? Just trying to wrap my head around it.
Thanks!
I got an app rejected on the samsung store for the exact same reason.
They even provided video recordings of the issue, and it is clear that on one device the scrollView is there, on the other it is not.
I can email you that video file, if you like.
That particular app was build with 2122
Cheers,
Tommy
This might be of some use information wise.
Starting with Graphics 2.0, widget.newScrollView is self-masking. Before if you did not specify a width and height, it would take up the whole screen and not need a mask. If you wanted the scrollView to occupy a smaller portion of the screen, you had to provide a mask. Since G2.0 uses a display.newContainer, it automatically creates a rectangular mask (and I think it does for full screen as well).
Depending on what you’re putting in side the scrollView, like, text, tableViews, etc. that also use masks, you can hit a **device dependent** limit on masking. Many devices it’s three units deep, some devices it’s only two. So it’s possible that what you’re seeing is hitting the mask limit on some devices.
Great news! Tested the scrollviews with build 2170, and it works in the test environment through the Samsung site on the device that it didn’t work on before, so I resubmitted the app update. We’ll see! I’ll keep you posted!
Dear Rob,
I am also having the issues with ‘white boxes’, where I have 1 scroll view with an added mask, and trying to add nested scroll views in it.
Since the scroll view automatically adds in a mask, what is the best method to implement multiple scroll views nested inside 1 main scroll view (to avoid the ‘white boxes’) ?
By the way, the scrollview document (http://docs.coronalabs.com/api/library/widget/newScrollView.html) needs to be updated to indicate this limitation.
Thanks
Hi @yosu,
The nested masking limitation is a hardware issue, so you’ll need to avoid exceeding the limit of three for best compatibility on all devices. Note the list of masked objects listed on the :setMask() documentation page:
http://docs.coronalabs.com/api/type/DisplayObject/setMask.html
I will add this note/gotcha to the scrollView and tableView pages soon.
Take care,
Brent
Dear Rob,
I am also having the issues with ‘white boxes’, where I have 1 scroll view with an added mask, and trying to add nested scroll views in it.
Since the scroll view automatically adds in a mask, what is the best method to implement multiple scroll views nested inside 1 main scroll view (to avoid the ‘white boxes’) ?
By the way, the scrollview document (http://docs.coronalabs.com/api/library/widget/newScrollView.html) needs to be updated to indicate this limitation.
Thanks
Hi @yosu,
The nested masking limitation is a hardware issue, so you’ll need to avoid exceeding the limit of three for best compatibility on all devices. Note the list of masked objects listed on the :setMask() documentation page:
http://docs.coronalabs.com/api/type/DisplayObject/setMask.html
I will add this note/gotcha to the scrollView and tableView pages soon.
Take care,
Brent