Skip to content

Added functionality to select swipeable directions#65

Open
kh0r wants to merge 1 commit into
Diolor:masterfrom
kh0r:master
Open

Added functionality to select swipeable directions#65
kh0r wants to merge 1 commit into
Diolor:masterfrom
kh0r:master

Conversation

@kh0r

@kh0r kh0r commented May 19, 2015

Copy link
Copy Markdown

I needed up/down functionality and made your library configurable - See #30. The default behaviour is still horizontal. But now you can change swipeable directions with the new direction attribute.

@kh0r kh0r mentioned this pull request Aug 2, 2015
@vleango

vleango commented Aug 6, 2015

Copy link
Copy Markdown

+1 Would love to have the 4 main directions swiping (up, down, left, right)

@maduperera

Copy link
Copy Markdown

Why isn't the commit conflicts have not been resolved. according to my understanding kh0r's solution has not been committed due to conflicts. So does that mean I can't use this library for swiping up and down. :(

@azhaguvel

Copy link
Copy Markdown

Hi
when i swipe right side without remove my finger open alert dialog i can able to swipe but i removed my finger after that cant able swipe please give solution

@neelmevada

neelmevada commented Dec 27, 2017

Copy link
Copy Markdown

@maduperera
when i am using app:direction="HORIZONTAL|VERTICAL"

it gives me below Error -
Error:(9) No resource identifier found for attribute 'direction' in package 'com.showbuddy'

My layout files are as below -

<com.lorentzos.flingswipe.SwipeFlingAdapterView
    android:id="@+id/frame"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    app:direction="HORIZONTAL|VERTICAL"
    app:rotation_degrees="15.5" />

Build.gradle has lines as below -
compile 'com.lorentzos.swipecards:library:1.0.9'

@ravinderpayal

Copy link
Copy Markdown

Why is this pull request still open? Please resolve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants