Hey guys
I have pages inside my scroll-view which provides an interactive "settings-mechanism".
What that means is my application will react to a vertical "swipe-gesture", and will change time-settings according to the scrollView-page.
This works very smooth and I'm quite happy as these are my first "kendo-UI steps".
Now the problem begins once you don't swipe straight, but your vertical movement is enough to trigger the "start page-change"-animation.
So what I need to do is to disable the scrollView, once the settings-adjustment got initiated.
My workaround is to disable this functionallity when I detect a more vertical swipe than a horizontal one (through dragstart & drag).
But this is not good for the enduser as he can start a settings-adjustment on the page and then change to a scrollView-page-transition with the same movement.
On my journey to find a solution, I was mainly looking for a way to achive these events/methods:
-Events:
AboutToChange (I don't understand the Changing-Event... It fires when the user already made a full transition... or is this a Chrome-Bug?)
Cancled
-Methods:
Enable / Disable the ScrollView
Like in the title mentioned, I thing these are quite essential things...I don't feel like I'm doing something very exotic here, or am I?
Maybe I'm missing something, because I can't find threads about that here, nor on stackoverflow.
So are there truely no workarounds / properties / whatever to "fix" my problem? Or should I change my widget with something else (maybe from the community?).
Thank you very much.
Cheers,
Richard
I have pages inside my scroll-view which provides an interactive "settings-mechanism".
What that means is my application will react to a vertical "swipe-gesture", and will change time-settings according to the scrollView-page.
This works very smooth and I'm quite happy as these are my first "kendo-UI steps".
Now the problem begins once you don't swipe straight, but your vertical movement is enough to trigger the "start page-change"-animation.
So what I need to do is to disable the scrollView, once the settings-adjustment got initiated.
My workaround is to disable this functionallity when I detect a more vertical swipe than a horizontal one (through dragstart & drag).
But this is not good for the enduser as he can start a settings-adjustment on the page and then change to a scrollView-page-transition with the same movement.
On my journey to find a solution, I was mainly looking for a way to achive these events/methods:
-Events:
AboutToChange (I don't understand the Changing-Event... It fires when the user already made a full transition... or is this a Chrome-Bug?)
Cancled
-Methods:
Enable / Disable the ScrollView
Like in the title mentioned, I thing these are quite essential things...I don't feel like I'm doing something very exotic here, or am I?
Maybe I'm missing something, because I can't find threads about that here, nor on stackoverflow.
So are there truely no workarounds / properties / whatever to "fix" my problem? Or should I change my widget with something else (maybe from the community?).
Thank you very much.
Cheers,
Richard