-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build issues - Swipe Gesture example does not show - most (maybe all) examples are empty #25
Comments
sorry about the reveal link. that’s an oversight on my part.
I’ll take a look at this, this evening - with a fresh clone, perhaps I’ve got some files missing.
|
Hi- I'll see if I can send a screencast - but very simply - SwipeGestureExample My first step was to just build the whole solution - and the Android build Then I tried the IOS project - it had build errors also - because of the [image: Inline image 1] thanks for your help. On Wed, Oct 21, 2015 at 6:00 PM, George Cook notifications@github.com
|
Here's the screencast On Wed, Oct 21, 2015 at 6:52 PM, Bert Beckmann bertbeck@gmail.com wrote:
|
I'm seeing this: [image: Inline image 1] On Wed, Oct 21, 2015 at 8:48 PM, Bert Beckmann bertbeck@gmail.com wrote:
|
Android version has compile errors.
For IOS - had to remove this linker option:
-gcc_flags "-F/Applications/Reveal.app/Contents/SharedSupport/iOS-Libraries -all_load -ObjC -framework Reveal -framework QuartzCore -framework CFNetwork"
I'm am trying to use/understand the swipegesture Forms
sample - when I run the IOS sample and click on Swipe - nothing happens. I trace the code - seems to call InitializeComponent() and controls seem to be initialized - but no nav page shows up - and no exceptions. I'm using Xamarin Studio Stable release, building on a Mac, Xcode 6.4
After further investigation - I trimmed the SwipeGestureExample.xaml to just the swipe left label and then commented out:
The page now comes up. Looks like the instantiation of gestures is somehow failing silently.
My shortened xaml is:
The text was updated successfully, but these errors were encountered: