Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

1.4.0 rc1: android - imageview inside view inside scrollableview doesn't get swipe event

this worked in 1.3.0!

also can't move to the next or previous view by setting/using the scrollableview's currentPage-property

the pagecontrol never shows up!

there is so much trial and error in ti-mobile at the moment, i'm seriously starting to think about learning objective-c and java for my future projects

if using the new image property inside the scrollableviews imageview the image never gets loaded

— asked June 22nd 2010 by Christian Sigl
  • android
  • currentpage
  • imageview
  • pagingcontrol
  • scrollableview
0 Comments

3 Answers

  • Opened Ticket 1183

    basically fixing touch events not getting into scrollable view broke swipe.

    — answered June 23rd 2010 by Don Thorp
    permalink
    1 Comment
    • i also have the problem, that views that are hidden and are behind a view are touchEnabled, even if i set touchEnabled to false. for an example i created a tabgroup-object on my own on android (it's based on standard ti-mobile views and some logic for enabling/disalbing means showing/hiding them), that consist of a view as a container per tab-content. when putting a view above it (even when not setting backgroundColor to transparent), the view that is hidden below receives touch events, so for an example tableviews inside views that are hidden are receiving clicks

      — commented June 23rd 2010 by Christian Sigl
  • would anyone of the devs please answer this question? i only can use the default swipe-gesture within the scrollableview on the view that is located behind the the image i'm displaying. this is very critical to my app!!!

    — answered June 23rd 2010 by Christian Sigl
    permalink
    0 Comments
  • not working on iPhone neither!!!???

    — answered July 5th 2010 by Marko Perutovic
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.