Scrollview and Samsung/Android devices

Solar2D General Questions/Discussion
#1

I am having an issue getting approved on the Samsung market due to my ScrollView Menus not showing up. I had a customer who contacted me who uses a Samsung Galaxy 3 Tablet 7 inch. All of the graphics are showing up and the listeners are working too; I tested this on an Android simulator through the Samsung Developer portal. The images inserted into the scrollview are not present.

 

Thoughts?

 

Thanks, Kiffin Ayers

#2

Hi Kiffin,

I’m checking with the engineers on this. In the meantime, can you specify in more detail what’s occurring? What kind of images are not showing up? What is their format and approximate image size? Are you applying any Graphics 2.0 filter effects on them?

Also, do you have your ScrollView “nested” within other masked objects? For example, is your ScrollView inside a container which is inside another container, or something like that? Devices have a varying “nested masking limit”, so this could be the issue.

Best regards,

Brent

#3

Thank you Brent. I read a bit before I posted where it was mentioned about the masking limit. The scrollView isn’t nested inside a container. The graphics are .png, which I use on everything. The dimensions are 100x100.

In the video sent by Samsung and on their online simulators, the images inside of the scrollView aren’t showing up at all. The Event Listeners are there and when I goto another screen, the images in those scrollViews aren’t present either. The images are used to make choices of displayed graphics.

The graphics are consistent on other devices, so this was a mild setback to see this.

Thanks, Kiffin

#4

Hi Kiffin,

Can you test this out in the most recent daily build (2130)? We addressed some internal things which may have been related to containers, alpha, etc.

Thanks,

Brent

#5

I was able to test another app on a device, and a new problem arose. I’m even having trouble in the simulator with the text in the Picker Wheel. It’s a bunch of blocks instead of numbers. I only have two columns with 100 numbers in each. I removed the titleBar and it fixed the Title text that was black boxed out.

I kept getting disconnected from the Samsung developer remote testing server. I’m using that since I don’t have the specific device that was presenting the issues.

Thanks, Kiffin

#6

I was able to get on a device this morning. The scrollViews are still not showing the content. The images that are called use a mask, and so I can’t tell if they are not showing up since the audio isn’t coming through the simulator. I’m not focused on the audio yet in case that is a separate issue.

Rob Miracle mentioned in another post that the next daily build was going to address an issue masking and widgets.

Thanks, Kiffin

#7

I’m also getting black text in scrollviews using 2014.2130 on the simulator. Haven’t tried devices yet, but this is bad enough. :frowning:

More precisely, the text renders as solid black rectangles. In some cases, the rectangles disappear and it renders properly when the scrollview is scrolling.

#8

Build 2130 has the black text problem.  It’s solved in 2135.

Rob

#9

You guys are awesome thanks!

#10

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!

#11

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

#12

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!

#13

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

#14

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.

#15

Hi Kiffin,

I’m checking with the engineers on this. In the meantime, can you specify in more detail what’s occurring? What kind of images are not showing up? What is their format and approximate image size? Are you applying any Graphics 2.0 filter effects on them?

Also, do you have your ScrollView “nested” within other masked objects? For example, is your ScrollView inside a container which is inside another container, or something like that? Devices have a varying “nested masking limit”, so this could be the issue.

Best regards,

Brent

#16

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!

#17

Thank you Brent. I read a bit before I posted where it was mentioned about the masking limit. The scrollView isn’t nested inside a container. The graphics are .png, which I use on everything. The dimensions are 100x100.

In the video sent by Samsung and on their online simulators, the images inside of the scrollView aren’t showing up at all. The Event Listeners are there and when I goto another screen, the images in those scrollViews aren’t present either. The images are used to make choices of displayed graphics.

The graphics are consistent on other devices, so this was a mild setback to see this.

Thanks, Kiffin

#18

Hi Kiffin,

Can you test this out in the most recent daily build (2130)? We addressed some internal things which may have been related to containers, alpha, etc.

Thanks,

Brent

#19

I was able to test another app on a device, and a new problem arose. I’m even having trouble in the simulator with the text in the Picker Wheel. It’s a bunch of blocks instead of numbers. I only have two columns with 100 numbers in each. I removed the titleBar and it fixed the Title text that was black boxed out.

I kept getting disconnected from the Samsung developer remote testing server. I’m using that since I don’t have the specific device that was presenting the issues.

Thanks, Kiffin

#20

I was able to get on a device this morning. The scrollViews are still not showing the content. The images that are called use a mask, and so I can’t tell if they are not showing up since the audio isn’t coming through the simulator. I’m not focused on the audio yet in case that is a separate issue.

Rob Miracle mentioned in another post that the next daily build was going to address an issue masking and widgets.

Thanks, Kiffin