pickerwheel does not work build 2288

Solar2D General Questions/Discussion
#1

hi there,

i was reading about all fixed pickerwheel issues and dl the latest night build.

just to find out, its worse than the old version. 

while fast scrolling it jumps to a nr. stops and than scroll back to another nr (over a range over 3-5 numbers)

i have a time to set… … here i could click bellow the select bar to increase one by one.

that works till the nr. 55 (from 60) than stops… 

also scrolling down lets say from 20 to 10… it goes to 10 and than jumps to 12

im using graphicsCompatibility = 1   and nightbuild 2288

just to mention :slight_smile:

hope u can fix that soon

btw… the pickerwheel worked fine with build 2100

attached a source to test … 

and if someone from corona can confirm… please put it in the bug report… im on travel and hardly online

chris

#2

Your code doesn’t look attached

#3

Hi,

same here (starting at a specific row is messed up).

Had to switch to the latest public release as a workaround.

I’m using Build 2014.2289 (without using graphicsCompatibility = 1)

Dan

#4

Ups… something went wrong :slight_smile:

here the source again…

.im using now build 2154 where the pickerwheel was just fine :slight_smile:

#5

Bug: 32531

#6

Rob 

thank u so much… 

hope it can be fixed soon

greets

chris

#7

Hi Rob,

when will the pickerwheel finally run as expected ??

sorry im really disappointed, how could u realise such a buggy thing and work on other ‘new’ things.

I downloaded today the latest daily build and still the wheel is jumping around and when i scroll down fast

it mess up completly by changing the align etc.

Could u not give that some priority that this works asap!!

Please, do not push new things while already released stuff keep buggy for month.

thanks

chris

#8

Chris, I know where you’re coming from.  However, here are things we have to come out with that may not seem important to you but are very important to other subscribers and business requirements.  When people are waiting on bug fixes, this can seem frustrating, but we still have to find a balance as we need to produce new features as well.

Rob

#9

i try to understand.

also it makes no sense to do something new, while something other users ALREADY have implemented stop working!!!

Its even more horrible. Something thats not implemented right now, cant do something bad and corona is now long in the market

and the features available are enough for most. for sure new gadgets are always funny.

but when something u rely on, something u already placed into ur app, invested hours of work, stop working or come unusable

that should be a absolutly priority to fix. 

#10

When we put out a new public build, we will focus on making sure we’ve fixed all the regression bugs.  Daily builds, by their very nature (we can’t run full batteries of tests or they wouldn’t be daily builds since it takes several days to run a full suite of tests) can introduce regression bugs and we will do our best to get them fixed.

If having a stable version to work from, then you should use and stay with public builds.  If you want to work with daily builds, you do get the latest features and fixes, and of course occasional regression bugs.

Rob

#11

Your code doesn’t look attached

#12

Hi,

same here (starting at a specific row is messed up).

Had to switch to the latest public release as a workaround.

I’m using Build 2014.2289 (without using graphicsCompatibility = 1)

Dan

#13

Ups… something went wrong :slight_smile:

here the source again…

.im using now build 2154 where the pickerwheel was just fine :slight_smile:

#14

Bug: 32531

#15

Rob 

thank u so much… 

hope it can be fixed soon

greets

chris

#16

Hi Rob,

when will the pickerwheel finally run as expected ??

sorry im really disappointed, how could u realise such a buggy thing and work on other ‘new’ things.

I downloaded today the latest daily build and still the wheel is jumping around and when i scroll down fast

it mess up completly by changing the align etc.

Could u not give that some priority that this works asap!!

Please, do not push new things while already released stuff keep buggy for month.

thanks

chris

#17

Chris, I know where you’re coming from.  However, here are things we have to come out with that may not seem important to you but are very important to other subscribers and business requirements.  When people are waiting on bug fixes, this can seem frustrating, but we still have to find a balance as we need to produce new features as well.

Rob

#18

i try to understand.

also it makes no sense to do something new, while something other users ALREADY have implemented stop working!!!

Its even more horrible. Something thats not implemented right now, cant do something bad and corona is now long in the market

and the features available are enough for most. for sure new gadgets are always funny.

but when something u rely on, something u already placed into ur app, invested hours of work, stop working or come unusable

that should be a absolutly priority to fix. 

#19

When we put out a new public build, we will focus on making sure we’ve fixed all the regression bugs.  Daily builds, by their very nature (we can’t run full batteries of tests or they wouldn’t be daily builds since it takes several days to run a full suite of tests) can introduce regression bugs and we will do our best to get them fixed.

If having a stable version to work from, then you should use and stay with public builds.  If you want to work with daily builds, you do get the latest features and fixes, and of course occasional regression bugs.

Rob