I have seen some applications that start up with a splash screen with a next button that when click makes another page roll in from the right. On those pages is usually a next or back button that lets a user go back to the first screen or proceed to the next.
I've not seen anything in the Xamarin examples on how to do this.
Would appreciate if someone could provide an example or give me some suggestions as to how I can do this.
Thanks
What you're looking for is CarouselView. It doesn't come bundled with the stable Xamarin.Forms installation so you'll have to download it separately or add through NuGet.
Here's the NuGet and the GitHub repository.
With the CarouselView, you can have multiple "pages" in the style of splash screen/onboarding screens that are popular these days.
Here's an article on how to use the control: https://blog.xamarin.com/flip-through-items-with-xamarin-forms-carouselview/
Edit: On another thought, I'd probably use the CarouselView implementation by GitHub user alexrainman. It has more features, is better tested and more mature.
Related
I have tried to get the data-role="backbutton" kendo mobile ui feature to work but I am having issues. When testing the app on my iPhone 4 I get stuck in my app because the back button breaks the UX.
What happens is that when I am testing, I click heaps of back buttons (as they are used quite heavily in my app) and then randomly one decides to slide the previous view into the screen but only goes halfway and then snaps back (or some other type of visual glitch occurs). Then after that, all my navigation breaks down and I get stuck in the last view that I was in. Or better yet the links go to places that they are not supposed to. My tab bar does not work and either do links in the header. I have to exit the app completely, remove it from operating and try again. Seriously something wrong going on here.
I have tried to programatically add the back button by following the Kendo UI documentation but that does not work either. I am left with a button that does absolutely nothing when clicked - it may not even solve the issue anyway. I have looked using developer console in Google Chrome but I can't see any obvious issues.
Has anyone using Kendo Mobile UI experienced this issue before?
I downloaded the latest release of the Kendo UI build and the problem seems to have been resolved. Surprising! I assumed the Kendo framework was a bit more mature to be experiencing such a big issue. It was occurring when using slide transitions in navigation. Here is a link to the bug post on Github https://github.com/telerik/kendo-ui-core/issues/66
I'm looking to add two finger "fluid swiping" to my app. Anyone who has used the week view in the Calendar app that comes with OSX will have seen what I'm trying to do.
I have a scroll view, and I want to be able to use swipe gestures and scrolling to move the content view in the horizontal axis of my NSScrollView, ie a day or a week.
The video from WWDC 2011 titled "Scrolling, Swiping, Dragging: Now with more animation" was quite useful, and looks like it will be able to explain what I want to do, but unfortunately the sample code for PictureSwiper isn't provided with the video.
I'm aware that a newer version of PictureSwiper is avaliable, but it uses NSPageController and I'm really looking for the older Lion 10.7 way of handling things as I can't use NSPageController. Is it still possible to find the old PictureSwiper somewhere?
If not could someone explain how the PictureSwiper sample on Lion worked? I'm aware of the App note https://developer.apple.com/library/mac/#releasenotes/Cocoa/AppKitOlderNotes.html (search for "scrollWheel:") but that has only gone part of the way to explaining the kind of functionality I am after.
Many thanks for any help.
David.
For anyone looking to this for an answer I eventually used one of my "Developer Technical Support" queries that came with my paid Dev account to ask for the old code. A few days latter an Apple engineer emailed me the old Picture Swiper.
Now that I have seen the code the App note makes complete sense! Picture Swiper moves CALayers around, but in my case I just use NSClipView's scrollToPoint:.
Within the scroll handler I just do something like: (gestureAmount * columnWidth) + currentColumnIndexOffset.
Seems to work!
I'm trying to build a Firefox add-on based on their SDK and I wanna use panel for this. The panel is connected to a widget, so every time I click on the widget icon the panel shows up.
My problem is that I want the panel to stay visible even if I click on an area outside the panel and to be able to close only based on a certain situations.
Can this be achieved, or the panel API doesn't support this?
Thanks
It can't be achieved through the SDK API. However, you could actually "hack" the panel in order to be persistent, the problem is that you will face with other issue – basically won't go away, and other small stuff.
You can get additional details on Bugzilla if you're interested: Add a "isPersistent" attribute for panels. Notice that the bug is a WONTFIX, but it will give you an idea about the issue you could face. Also, there are some new widgets that will coming in the future, that could mitigate the needs to have the panel "persistent" (they're mentioned and linked in the bug above).
This is the offical sdk method of doing it:
let myPanel = Panel({.....})
let { getActiveView }=require("sdk/view/core");
getActiveView(myPanel).setAttribute("noautohide", true);
Floating panels are not supported by the SDK
Is there a way to create a wizard-like window in SketchFlow 4?
it needs the standard prev/next buttons, and of course the "Finish" button on the last page.
Are you having problems creating that? Sounds like a straightforward use of the prototyping features in SketchFlow. Simply link the sequence of screens together and use buttons with navigation behaviors to navigate between the screens.
I'm doing the same thing right now. We came at it two different ways - up to you which you prefer.
One is to use a TabControl and use the tabs as the steps of the wizard. This means you don't have to deal with adding the nav links back and forth, but you might have trouble getting the look you're hoping for.
The other way, as Chuck mentions, is just to essentially clone each step of the wizard screen as its own individual SketchFlow screen, with just the content section changed. Then you can link up each screen with the navigation hooks in the SketchFlow Map.
The latter is certainly more customizable, and once you get the hang of how to reuse sections of your design, tends to work better.
mostly in all article i found that everyone show that their OS give them 5 button. can anyone explain how
http://www.asp.net/mvc/tutorials/getting-started-with-mvc3-part1-cs
in this article every window's title bar have 5 button on top whenever i can see only three button in my windows [close, restore ,maximize].
can anyone show me reason behind it.
They're running UltraMon, which is a utility that provides enhancements for multiple monitor support.
In particular, it adds extra window management buttons to the title bars of all applications, which make it easy to move windows from screen to screen.
You can download a free evaluation version from the vendor, but the full version will cost you $39.95 US.
He has multiple screens on his computer, those buttons mean move to next screen.
Extra buttons in the titlebar come from utility applications that hook into every process.
Take a look at this tutorial for a basic example, you also need to register a hook with SetWindowsHookEx (WH_CBT or WH_SHELL)
For Windows Vista and 7, Microsoft has provided detailed guidance in the article Custom Window Frame Using DWM.
Copied from my answer here.