Widget 2.0 - Tableview - Android Build - Release/press Event Issues

Solar2D Widgets
#21

Yea this touch responsiveness is a bit of a show-stopper.  Be really nice to see the responsiveness addressed in a daily build soon.  Really cannot release things with the way the row touch events work just now.

Cheers

#22

Are we talking about the tap events here or the press/hold events?

#23

Perhaps i missed it in the documentation but i do not see any Tap support.  The docs say: press, release, swipeLeft, swipeRight.

The Widget 1.0 had an event ‘tap’ which i do not see anymore.  From my perspective i dont really care if you put tap back in or not but currently you have to press-hold-release to get get the release event to fire.  Without the “hold” part of that action the release event is not firing.

#24

You are right, there isn’t currently a tap event. I will add that. I was just asking if this was the problem (the lack of a tap event) that you guys were talking about.

#25

Yep thats it danny. A Tap would be great, i’ve had four people testing an app i’m working on and they all mentioned it was hard to press the rows in the tableViews.

Also, i’ve noticed in recent builds that the swipeLeft and Right aren’t working properly (In my opinion), you have to do it super fast for it to actually work as intended.E.g. if you do a slow swipe all three events fire, which seems to be cancelling out the swipe. 

–press

–swipeRight

–release

Whereas if you do it super fast (which no one does) only the “swipeRight” is displayed as the phase and it works correctly and shows my delete button. The phases being printed seem to be a bit misleading, as if it said it fired you would expect to see your delete button appear, but it doesn’t… 

The strangest part of all (sorry this is going on a while lol), is that if you do the slow swipe which fires all three events and move the table view up or down even slightly the swipe registers correctly and the delete button appears… Strange!

Has anyone else noticed that? I swear it wasn’t doing that a few builds ago.

I was going to do a bug report on it but i wasn’t sure if its just me doing something strange :smiley:

#26

+1 it’s very difficult to press row…

need “tap” emergency

I am using tap in all my apps…

thanks

I found another important issue

I cant drag my tableview on “Category” row

that’s if i set “isCategory = true” 

that row i can’t drag…that’s looks like my table view is broken.

sometimes can drag  sometimes not…

and first row sometimes get nil parameter on “isCategory”

pleas fix it ASAP!! thanks!!

#27

A tap event has been added and will be in your hands shortly. Thanks

See my comment above :slight_smile:

#28

another critical bug about row.!

Can’t delete row correctly!

I alter it from Sample ListView1

change default size from 20 to 5

  local function onRowTouch( event )     local phase = event.phase --    local row = event.target     local row = event.row     if "press" == phase then         print( "Pressed row: " .. row.index )       elseif "release" == phase then         -- Update the item selected text         itemSelected.text = "You selected item " .. row.index                  --Transition out the list, transition in the item selected text and the back button --        transition.to( list, { x = - list.contentWidth, time = 400, transition = easing.outExpo } ) --        transition.to( itemSelected, { x = display.contentCenterX, time = 400, transition = easing.outExpo } ) --        transition.to( backButton, { alpha = 1, time = 400, transition = easing.outQuad } )                          print("event.row.index",event.row.index)                 print("event.target.index",event.target.index)         print( "Tapped and/or Released row: " .. row.index )                 list:deleteRow(event.target.index)     end end
#29

PS: event.target is the row, event.row is nil as it doesn’t exist.

#30

it exists.

i run it on 1076.

i also tried “event.target.index” . got same situation

#31

event.target.index will not work anymore with widget 2.0 … 

It is likely that i just don’t get what your trying to communicate but … before Widget 2.0 you would use:

event.target to get the row

and

event.target.index to get the index

Now with Widget 2.0 you MUST change that to use:

event.row to get the row

and

event.row.index to get the index

#32

Just stumbled across your last post Danny, if you could get the touch or tap events to be more responsive on the rows that would be great.

Its really quite hard to select rows currently and i can’t see a way that we can edit it to make it any better. Thanks!

#33

Yea this touch responsiveness is a bit of a show-stopper.  Be really nice to see the responsiveness addressed in a daily build soon.  Really cannot release things with the way the row touch events work just now.

Cheers

#34

Are we talking about the tap events here or the press/hold events?

#35

Perhaps i missed it in the documentation but i do not see any Tap support.  The docs say: press, release, swipeLeft, swipeRight.

The Widget 1.0 had an event ‘tap’ which i do not see anymore.  From my perspective i dont really care if you put tap back in or not but currently you have to press-hold-release to get get the release event to fire.  Without the “hold” part of that action the release event is not firing.

#36

You are right, there isn’t currently a tap event. I will add that. I was just asking if this was the problem (the lack of a tap event) that you guys were talking about.

#37

Yep thats it danny. A Tap would be great, i’ve had four people testing an app i’m working on and they all mentioned it was hard to press the rows in the tableViews.

Also, i’ve noticed in recent builds that the swipeLeft and Right aren’t working properly (In my opinion), you have to do it super fast for it to actually work as intended.E.g. if you do a slow swipe all three events fire, which seems to be cancelling out the swipe. 

–press

–swipeRight

–release

Whereas if you do it super fast (which no one does) only the “swipeRight” is displayed as the phase and it works correctly and shows my delete button. The phases being printed seem to be a bit misleading, as if it said it fired you would expect to see your delete button appear, but it doesn’t… 

The strangest part of all (sorry this is going on a while lol), is that if you do the slow swipe which fires all three events and move the table view up or down even slightly the swipe registers correctly and the delete button appears… Strange!

Has anyone else noticed that? I swear it wasn’t doing that a few builds ago.

I was going to do a bug report on it but i wasn’t sure if its just me doing something strange :smiley:

#38

Danny,

Working with 1080 and not seeing this TAP support.  I do not see anything in the documentation that suggests how to access this support for tap.  I tried adding an onRowTap listener but that does not seem to be the ticket.

Can you let us know how to access the Tap handling on the tableview rows?

Thanks,

m

#39

The changes didnt make it into 1080. When they do you will se the widget related notes in the release notes for that daily build.

The support is added (as is the other stuff i mentioned like row performance) i will find out what daily build the changes will be added in.

Thanks

#40

As it was said before it’s very difficult to press a row.

I can add a “tap” listener when creating the row, but if row was taped when scroll is happening the scroll stop (as it should ) but the tap event is dispatched (and it shouldn’t), the event should only be dispatched when the table isn’t scrolling.