Widget slider runtime error

Solar2D Daily Builds and Public Releases
#1

I was wondering if there have been changes to the way a widget slider is implemented?  I have not made any code changes, I only downloaded a new daily build.

release used: 2017.3044  (did not use 3043 because on a mac and had the disk image error)

I have since tried 3046, 3047 and 3048 releases and I still have the same error

When the slider is initialized I now get a runtime error.

ERROR: Runtime error

?:0: attempt to perform arithmetic on field ‘x’ (a nil value)

stack traceback:

?: in function <?:448>

(tail call): ?

?: in function <?:119>

(tail call): ?

/Volumes/TOSHIBA EXT/CoronaDevelopment/BlockR/View/options.lua:229: in function ‘?’

?: in function ‘dispatchEvent’

?: in function ‘showOverlay’

/Volumes/TOSHIBA EXT/CoronaDevelopment/BlockR/View/mainmenu.lua:89: in function ‘_onEvent’

?: in function ‘?’

?: in function ‘?’

?: in function <?:182>

Handling the unhandled error ?:0: attempt to perform arithmetic on field ‘x’ (a nil value)

This happens at the following code: (portion of code included in pdf)

musicSlider = widget.newSlider(options)

It will then place the slider up in the top left hand corner.

I do use my own image sheet for the slider. But once again I have not changed my program code.  I have defaulted back to release 2017.3040 where the slider works with no problem.

Since changes were made to the slider in release 3043 I was wondering if something has changed in the way the slider is set up?  I looked for any information online and have not found anything.

#2

There was a change in 3043 to fix a bug where the position of the slider would change if the handle was too close to an edge when created making it hard to position.  

Can you post the code for your slider creator function?

Thanks

Rob

#3

My code is as follows:

local sliderSheetInfo = require(“Images.options.optionsSlider2”);

 

local sliderSheet = graphics.newImageSheet( path … “optionsSlider2.png”, sliderSheetInfo:getSheet() );

 

– Create the widget

local sliderOptions =  {

       sheet = sliderSheet,

       leftFrame = 1,

       middleFrame = 2,

       rightFrame = 5,

       fillFrame = 3,

       frameWidth = 4,

       frameHeight = 12,

       handleFrame = 4,

       handleWidth = 28,

       handleHeight = 28,

       orientation = “horizontal”,

       width = 80,

       listener = sliderListener

   };

 

– local variable musicSlider declared at beginning of code

musicSlider = widget.newSlider(sliderOptions);

musicSlider.id = “musicVol”;

musicSlider:setValue(currentMusicVol);

musicSlider.x = musicVolLabel.x + musicSlider.width + 10 ;

musicSlider.y = musicVolLabel.y - (musicVolLabel.height - musicSlider.height) + 2;

sceneGroup:insert( musicSlider );

** for the image sheet it is just as follows

local SheetInfo = {}

 

SheetInfo.sheet =

{

    frames = {

    

        {

            – sliderLeft

            x=1,

            y=1,

            width=4,

            height=10,

 

        },

        {

            – sliderBar

            x=4,

            y=39,

            width=4,

            height=10,

 

        },

        {

            – sliderFill2

            x=1,

            y=77,

            width=6,

            height=6,

 

        },

        {

            – sliderGear

            x=1,

            y=104,

            width=43,

            height=46,

 

        },

        {

            – sliderRight

            x=104,

            y=1,

            width=4,

            height=10,

 

        },

    },

    

    sheetContentWidth = 110,

    sheetContentHeight = 151

}

 

SheetInfo.frameIndex =

{

 

    [“sliderLeft”] = 1,

    [“sliderBar”] = 2,

    [“sliderFill2”] = 3,

    [“sliderGear”] = 4,

    [“sliderRight”] = 5,

}

 

function SheetInfo:getSheet()

    return self.sheet;

end

 

function SheetInfo:getFrameIndex(name)

    return self.frameIndex[name];

end

 

return SheetInfo

** Now I am wondering after reading how the position of the handle was changed, if my settings that started with the handle at 0 would cause that problem.  I am using data that was already saved that I read in thru a JSON file.  I previously had the slider bar handle at 0 so I wouldn’t hear the sound for now during testing.  But I cannot see how starting the handle at 0 percent would give me an error unless how the values are seen by the widget have changed.

#4

Forget that last comment about starting the handle at 0.  I tested ver 3048 with the value for the handle starting in the middle, still received the same runtime error.  Back to ver 3040 for now.

#5

Hi @mlab,

This is because you didn’t specify any positional attributes for your slider in the constructor (neither x/y nor top/left). You’re supposed to do that, but the widget library doesn’t prevent you from omitting them, so it’s not really your fault (its ours).

Short-term fix: you can supply an x/y or top/left for the sliders in your constructor, even if just 0/0, and reposition them afterward. Or, you can wait for an upcoming daily build where the issue will be fixed.

Best regards,

Brent

#6

Hi Brent,

That seemed to work.  Since I declare x and y later after I created it and it worked with previous builds, it never occurred to me that would be my issue.  I added the x/y at 0/0 in my constructor, then re-positioned them and everything works now with build 2017.3048.

Thank you very much for your help.

ML

#7

Hi @mlab,

This should be fixed in daily build 2017.3052 or later, if you’d like to test it there (so, no modifications necessary to the code you had previously been using).

Brent

#8

Hi Brent,

Sorry for the late reply, I did go back to the previous code with the new build to test it and everything runs fine that way.

Thanks - Mel

#9

There was a change in 3043 to fix a bug where the position of the slider would change if the handle was too close to an edge when created making it hard to position.  

Can you post the code for your slider creator function?

Thanks

Rob

#10

My code is as follows:

local sliderSheetInfo = require(“Images.options.optionsSlider2”);

 

local sliderSheet = graphics.newImageSheet( path … “optionsSlider2.png”, sliderSheetInfo:getSheet() );

 

– Create the widget

local sliderOptions =  {

       sheet = sliderSheet,

       leftFrame = 1,

       middleFrame = 2,

       rightFrame = 5,

       fillFrame = 3,

       frameWidth = 4,

       frameHeight = 12,

       handleFrame = 4,

       handleWidth = 28,

       handleHeight = 28,

       orientation = “horizontal”,

       width = 80,

       listener = sliderListener

   };

 

– local variable musicSlider declared at beginning of code

musicSlider = widget.newSlider(sliderOptions);

musicSlider.id = “musicVol”;

musicSlider:setValue(currentMusicVol);

musicSlider.x = musicVolLabel.x + musicSlider.width + 10 ;

musicSlider.y = musicVolLabel.y - (musicVolLabel.height - musicSlider.height) + 2;

sceneGroup:insert( musicSlider );

** for the image sheet it is just as follows

local SheetInfo = {}

 

SheetInfo.sheet =

{

    frames = {

    

        {

            – sliderLeft

            x=1,

            y=1,

            width=4,

            height=10,

 

        },

        {

            – sliderBar

            x=4,

            y=39,

            width=4,

            height=10,

 

        },

        {

            – sliderFill2

            x=1,

            y=77,

            width=6,

            height=6,

 

        },

        {

            – sliderGear

            x=1,

            y=104,

            width=43,

            height=46,

 

        },

        {

            – sliderRight

            x=104,

            y=1,

            width=4,

            height=10,

 

        },

    },

    

    sheetContentWidth = 110,

    sheetContentHeight = 151

}

 

SheetInfo.frameIndex =

{

 

    [“sliderLeft”] = 1,

    [“sliderBar”] = 2,

    [“sliderFill2”] = 3,

    [“sliderGear”] = 4,

    [“sliderRight”] = 5,

}

 

function SheetInfo:getSheet()

    return self.sheet;

end

 

function SheetInfo:getFrameIndex(name)

    return self.frameIndex[name];

end

 

return SheetInfo

** Now I am wondering after reading how the position of the handle was changed, if my settings that started with the handle at 0 would cause that problem.  I am using data that was already saved that I read in thru a JSON file.  I previously had the slider bar handle at 0 so I wouldn’t hear the sound for now during testing.  But I cannot see how starting the handle at 0 percent would give me an error unless how the values are seen by the widget have changed.

#11

Forget that last comment about starting the handle at 0.  I tested ver 3048 with the value for the handle starting in the middle, still received the same runtime error.  Back to ver 3040 for now.

#12

Hi @mlab,

This is because you didn’t specify any positional attributes for your slider in the constructor (neither x/y nor top/left). You’re supposed to do that, but the widget library doesn’t prevent you from omitting them, so it’s not really your fault (its ours).

Short-term fix: you can supply an x/y or top/left for the sliders in your constructor, even if just 0/0, and reposition them afterward. Or, you can wait for an upcoming daily build where the issue will be fixed.

Best regards,

Brent

#13

Hi Brent,

That seemed to work.  Since I declare x and y later after I created it and it worked with previous builds, it never occurred to me that would be my issue.  I added the x/y at 0/0 in my constructor, then re-positioned them and everything works now with build 2017.3048.

Thank you very much for your help.

ML

#14

Hi @mlab,

This should be fixed in daily build 2017.3052 or later, if you’d like to test it there (so, no modifications necessary to the code you had previously been using).

Brent

#15

Hi Brent,

Sorry for the late reply, I did go back to the previous code with the new build to test it and everything runs fine that way.

Thanks - Mel