ScrollView event.direction not available until event.limitReached = true...

Solar2D Widgets
#1

Hi,

If you look at the WidgetDemo tab2 and place a print(direction) in the scrollView event listener you will notice that the event.direction = nil as you move the scrollView until you reach the scrollLimit in any direction. 

The API document says : 

Listener. Used to listen for ScrollView events, with the following events: event.limitReached - Indicates that the scrollView has reached one of it’s limits. event.direction - Returns the direction the scrollView is moving in.

The way I read the API document tells me I should be getting event.direction firing through out the scrollView movement and event.limitReached right at the end. Currently this is not the case. 

Thanks & best regards,

Kerem

#2

Adding to this issue…

if you have horizontalScrollDisabled = true because your content is one screen wide then you never get event.limitReached = true. In other words when you try to move the scrollView you get event.direction = nil firing off so the scrollView detects movement attempt which is great but the end of scrollView scroll range reached event never fires. A little challenge to overcome.

Thanks much for your help.

#3

Finally…

if I slowly push the scrollView to its limit it appears that event.limitReached = true does not occur. If I flick the scrollView and let it bounce against the edge then the event.limitReached fire off true right away. For this event to be truly useful it should be detected regardless of how fast the scrollView was moved. 

#4

Hi Kerem,

I presented this to the engineers. Should be checked and fixed soon, I imagine. Thanks for the detailed report and description of the exact behavior.

Brent

#5

Hi Brent, 

Thanks much for the update. I appreciate all the effort going into the widgets. Life is good! :slight_smile:

Regards,

Kerem

#6

Adding to this issue…

if you have horizontalScrollDisabled = true because your content is one screen wide then you never get event.limitReached = true. In other words when you try to move the scrollView you get event.direction = nil firing off so the scrollView detects movement attempt which is great but the end of scrollView scroll range reached event never fires. A little challenge to overcome.

Thanks much for your help.

#7

Finally…

if I slowly push the scrollView to its limit it appears that event.limitReached = true does not occur. If I flick the scrollView and let it bounce against the edge then the event.limitReached fire off true right away. For this event to be truly useful it should be detected regardless of how fast the scrollView was moved. 

#8

Hi Kerem,

I presented this to the engineers. Should be checked and fixed soon, I imagine. Thanks for the detailed report and description of the exact behavior.

Brent

#9

Hi Brent, 

Thanks much for the update. I appreciate all the effort going into the widgets. Life is good! :slight_smile:

Regards,

Kerem

#10

Any news on this bug? I need to know which way my scrollView is travelling - I’m having to use a workaround using event.y and event.yStart to calculate the direction.

#11

Yes, adding to this - can you get the bug fixed please?

#12

Hi guys,

In the works, update follows.

Alex

#13

Hi Alex, 

Any eta on the next batch of widget fixes? We are waiting with our breath held. Thanks much for all your hard work. 

Regards,

Kerem

#14

Hey Kerem,

I’m fixing some more bugs so that i can have a good batch ready. I still don’t have a clear ETA, but it should be soon.

Thanks,

Alex

#15

Hey Alex,

Thats wonderful news!!! Thanks so much for your hard work. Looking forward to that release. 

Regards,

Kerem

#16

Any news on this bug? I need to know which way my scrollView is travelling - I’m having to use a workaround using event.y and event.yStart to calculate the direction.

#17

Yes, adding to this - can you get the bug fixed please?

#18

Hi guys,

In the works, update follows.

Alex

#19

Hi Alex, 

Any eta on the next batch of widget fixes? We are waiting with our breath held. Thanks much for all your hard work. 

Regards,

Kerem

#20

Hey Kerem,

I’m fixing some more bugs so that i can have a good batch ready. I still don’t have a clear ETA, but it should be soon.

Thanks,

Alex