Widget 2.0 newStepper NO decrementing

Solar2D Widgets
#21

Hi Frank,

This is actually a “regression” bug. Stepper worked fine when W2 was released, because I wrote the tutorial on Stepper, tested it, and it functioned exactly as it’s supposed to. I don’t know exactly how/when this issue slipped in, but I’ll make sure it gets resolved in a daily build upcoming very soon, as in next week at the latest.

Brent

#22

I opened two tickets regarding this

Case 23372  

Case 23373 - is the more severe one, as no workaround !!!

This above behaviour shows when

a. you change the reference point. WA : set rp to CenterRp

b. you nest widget deeply in displayGroups. WA : n.a.

best

frank

#23

Thanks Frank, I’ll check into both of these tomorrow. :slight_smile:

#24

Brent, thanks. Please make sure you prioritize Case 23373. Thanks

#25

Hello @ale and Frank,

I investigated all of these issues, and the common factor is that adjusting the reference points of Steppers (off the center point) is not supported. This applies to adjusting the reference points of groups that Steppers are contained in too (i.e. setting a group’s reference point to center, versus the normal top-left). Essentially, the touch location of the Steppers are based on the coordinates of the press in content space versus the position of the stepper. If you shift around the reference points of the Steppers and/or the groups off their “normal”, it tweaks the input coordinates given to the Stepper, which explains (@ale) why it appeared that the decrementing isn’t working.

So, long story short: we are likely going to fix Stepper to not be based on reference points, but it won’t happen overnight. This has been added to the “to do” list, but it will likely happen after some of the higher priority tasks are implemented for W2.0.

Best regards,

Brent

#26

Brent,
 
thanks for your feedback.
 
I don’t completely agree with this. On top of the reference point issues, case 23373 is not using a single call to setReference point. This example states that deeply nesting (more than 1 group deep) is causing the issues.

Did you see this ?
Thanks
Frank

#27

Brent, any comment on this ? Can you reproduce 23373 and confirm that deeply nesting also causes this issue ?

thanks
Frank

#28

Hi Frank,

I’ll check into this tomorrow. I can’t recall the entire sample you submitted at this moment, but if you did any kind of manipulation of any group or nested group that contains the Stepper (x or y shift or scaling) then this is likely the issue. I’ll check out the code again tomorrow.

Take care,

Brent

#29

Hey Frank, 

I have fixed both of these bugs and the fixes should be available to you shortly via daily builds.

Thanks

#30

Thanks Danny. I will test and confirm once available.

#31

Danny, preliminary tests show that the widget itself works. However, a new bug was introduced that makes the widgets react very slowly. I reported the bug : Case 23427. 

Frank

#32

Danny,

the bug went away after uninstalling CL, installing the latest public build and then installing 1106.

Best
Frank

#33

Hello Brent, Danny and Frank,

thanks for yours investigations and fixing. 

I have just download the daily 1108 and the steppers are working well…Thanks!!

I have an app that has a large use of widgets library, and seem that a lot of things are fixed now.  

I did not think that steppers are using coordinates in order to perform incr/decr… but make sense! :slight_smile:

Unfortunately other bugs are still open, I have a component in my app that use a newPickerWhell with a columColor that is not yet fixed.

http://forums.coronalabs.com/topic/33313-widget-20-newpickerwheel-columncolor-not-working-in-daily-build-1074/

Thanks anyway!

Ale