Help : widget.newSlider() spritesheet not working on devices

Solar2D General Questions/Discussion
#1

Hi 

We are creating a slider with a custom imageSheet. On the simulator (Windows and iOS) our custom slider is displayed properly. On the device on the other hand a strange blue pattern is displayed on Android and nothing on iOS.

Below you will find the code. Do we need to setup the theme ? If so, why ? as on the simulator it is working and based on the slider API, we provide the imageSheet.

Please help.

– Image sheet options and declaration

        local options = {

            frames = {

                { x=0, y=0, width=16, height=35 },

                { x=40, y=0, width=16, height=35 },

                { x=80, y=0, width=16, height=35 },

                { x=124, y=0, width=16, height=35 },

                { x=168, y=0, width=35, height=35 }

            },

            sheetContentWidth = 203,

            sheetContentHeight = 35

        }

        local sliderSheet = graphics.newImageSheet( “sliderSheet.png”, options )      

   

        – Create the widget

        slider = widget.newSlider

        {

            sheet = sliderSheet,

            leftFrame = 1,

            middleFrame = 2,

            rightFrame = 3,

            fillFrame = 4,

            frameWidth = 16,

            frameHeight = 35,

            handleFrame = 5,

            handleWidth = 35,

            handleHeight = 35,

            top = screen.topBar + 4,

            left = screen.x + 10,

            orientation = “horizontal”,

            width = screen.rw - 20,

            listener = sliderListener

        }

        group:insert( slider )

#2

Hi @nmichaud,

This sounds like you may have exceeded the device’s masking limit. Are you masking the slider group and nesting it down in other masked objects like a container, tableView, or scrollView?

Which build # are you using?

Brent

#3

Hi @Brent, we are using build 2282 and no, the slider is not inside other nested object, nor we are using mask. We have try instantiating the slider directly in its own group without any other objects and we have the same problem.

On the android, it seems it is using the android theme (but its completely weird, like its trying to take our value but not our imagesheet). How can it be as we are providing our own sheet. Do we still need to create a folder theme and put our imagesheet in it ? and call settheme ?

#4

This may be a visual bug that will be fixed in the next batch of widget fixes, which should be coming soon. Can you post your sheet image here so I can test on my side?

Thanks,

Brent

#5

Yes, here it is :

slidersheet.png

#6

Hi @nmichaud,

I tested your slider on iOS7 using Corona build #2189, and it works fine… I see the slider and I can manipulate it as expected. I haven’t tested on Android. Perhaps there’s some conflict with another theme file being declared (or not declared), or perhaps are you using an older build of Corona?

Brent

#7

@Brent, we are using a more recent build #2282. Are you calling setTheme to make it work ?

#8

I didn’t call setTheme. Also, I tested in #2303 and it looked fine.

#9

Well I really don’t understand how it works on your side. 

Here is a small test app for you to test (click to download)

This demo will show you that on windows simulator it is working. If you build the app, run it on Android Samsumg S3 if will not work. Here is 2 screenshots showing it running :

outputslider.png

#10

I would really appreciate if anybody else could try the code I have posted just before this one and tell me if it works for you. We do not understand why it is not working.

#11

Hi @nmichaud,

I notice you did not name the sheet file properly, which is probably why it’s breaking (it can’t find the sheet). You have it “sliderSheet.png” in the code and “slidersheet.png” as the file name. Files must be case-sensitive matches in every case. The Simulator can be more forgiving of this (which explains why it might work in the Simulator), but devices are not forgiving and require the case match.

Brent

#12

Oh no… I am so sorry. How come I did not see that. basic error, Sorry for the noise, I will go and hide in the corner for a few hours

#13

Brent just beat me to the line… I was coming back to post my results. Even the simulator (2014.2316) is now complaining about this : 

ERROR: The resource file (sliderSheet.png) could not be found at case-sensitive path (/Users/xxxxxx/Desktop/Slider Test/sliderSheet.png).

Warning: /Users/xxxxxx/Desktop/Slider Test/main.lua:21: Failed to find image ‘sliderSheet.png’

Its great that the simulator is not as forgiving as before so you can catch these issues quickly. All the best.

#14

If you have the “showRuntimeErrors” setting enabled on the simulator settings page… Does an error like this now halt the simulation and throw an error popup on the screen?

That would be handy.

Cheers

#15

There is no error popup on screen but the simulation is now halted and simulator shows you a black screen. When you look at the simulator logs you see the error I posted above. So the simulator no longer covers the capitalization mistakes you make. This is good.

#16

Thanks for the info, that is much more helpful.

What build did this behaviour change first happen in?

#17

I observed this behaviour on #2316 and @nmichaud says above that he tested his code in build #2282 and obviously he wasn’t presented with this error message. So in nutshell it must have been introduced somewhere between #2282 and #2316. Hope this helps.

#18

Hi @nmichaud,

This sounds like you may have exceeded the device’s masking limit. Are you masking the slider group and nesting it down in other masked objects like a container, tableView, or scrollView?

Which build # are you using?

Brent

#19

Hi @Brent, we are using build 2282 and no, the slider is not inside other nested object, nor we are using mask. We have try instantiating the slider directly in its own group without any other objects and we have the same problem.

On the android, it seems it is using the android theme (but its completely weird, like its trying to take our value but not our imagesheet). How can it be as we are providing our own sheet. Do we still need to create a folder theme and put our imagesheet in it ? and call settheme ?

#20

This may be a visual bug that will be fixed in the next batch of widget fixes, which should be coming soon. Can you post your sheet image here so I can test on my side?

Thanks,

Brent