Windows-8 FlipView issue with touch? - windows-8

I am running Windows 8 Consumer Preview and having an issue with the FlipView control.
In the Windows 8 SDK Sample pack (for Consumer Preview), there is a Controls_FlipView project that shows different things that can be done with the FlipView control. If I run the project in the Simulator and use the touch pointer (hand) and try flipping through the slides, if I flip relatively quickly, the FlipView sometimes ends the animation in between two slides, after letting go of the mouse. This also happens in a FlipView control in my own app.
screenshot: http://i39.tinypic.com/noa3o2.png
Is this a quirk/bug of the simulator? Or does this also happen on a real tablet? (I don't have one to check)

Related

Hiding navigation bar causes unexpected extra space in the bottom of the screen

I develop application both with WPF and GTK platforms using Xamarin forms. I decided to hide the default navbar using NavigationPage.HasNavigationBar="False", but after that, I got an extra space at the bottom of the app window. On WPF everything works good, this bug occurs only in GTX platform.
It looks like this navbar became transparent and moved to the bottom.
Here is the link to the picture https://i.stack.imgur.com/JrtlT.png
On Windows app everything works good, this bug occurs only in Linux app.
Not understanding occurs in Linux app .
By the way , if want to hide NavigationBar in forms , as follow will work :
NavigationPage.SetHasNavigationBar(this,false);

Flipview without rubber band effect at edge in Windows Phone 8.1

I am developing an app, which has 3 screens in first page as flipview items. Two screens has gridview & last screen contains camera. I want to develop nearly same UI as 6snap from Rudy Huyn.
In that it has camera in middle & two gridview (data view) at the ends. It doesn't have elastic band effect while swiping from one screen to another & it seems he has used flipview. I have chose flipview because it has selection change event & I can dispose camera resources efficiently. If my UI control choice is wrong let me know. I have tried to play manipulation events of flipviewitem but it doesn't work as expected. Any one out there who can guide me to develop the same flipview as 6snap.
Please check out my answer here:
ScrollViewer: Disable Snap (elastic band effect)
Maybe you will need to implement a different logic when to disable, and when to enable ManipulationMode, but it is possible

Windows 8 Image Slider

Is the image slider that the Windows 8 Camera app uses available as a control within the framework? It has nice transitions between images and provides previous and next buttons.
There is callisto refernce in nuget there you can find flipview like windows 8 app store
There is a FlipView control if you are referring to that.
You have some similar controls already built-in, such as FlipView if you want the previous and next buttons.
But if you want all the features in the image gallery application (with zooming capabilities), you will have to create your own component. I did, and it was quite painful, but sadly I did not have the time to package it properly to share with the community. Maybe someone else did it.

Windows Metro Apps on touch Screen Monitors

I know this might seem odd, but I am working on a windows Metro app which would be displayed on touch screen monitors in our local university.
Now I am using the simulator for debugging, but in the simulator you have to start "Touch Mode" to even use the touch interface.
So when using the touch monitors, do we have to specifically specify touch mode ? Or it will automatically integrate the touch functionality ?
Thank you.
Touch is a first class-citizen in Windows Store applications, so no special accommodations are needed. I would recommend you test on a touch device though before deploying, it's a different way of interacting, and even though the simulator does a decent job of handling the mechanics, it will "feel" different to a user - especially if you're leveraging pinch-zoom, swipe and other gestures.
On another note... is this app intended for a kiosk-type application? If so, keep in mind with Windows 8/RT, you won't be able to easily prevent the users from swiping to the charms, navigating to other programs, etc. You may want/need to take a look at Windows 8 Embedded depending on the specific deployment requirements.

Making a full screen Cocoa app

I want to create a full Screen Cocoa application, however my app is slightly different from a conventional fullscreen app.
This app would be below everything else, so underneath the menu bar and the Dock, etc. It would have a large image covering up the Desktop and icons, with a custom NSView in the middle with a table view, etc. If this concept is hard to understand then here is an image:
http://img10.imageshack.us/img10/6308/mockupo.png
The only part that might be a bit confusing is the background image. This background image is NOT the wallpaper of the computer, but part of the app. So when the app is launched, it goes into full screen mode and puts itself underneath the dock and the menu bar, and underneath all other windows too. So it draws the background image to cover the screen (including Desktop and icons). Then has a custom NSView in the middle containing my controls.
What's the best way to go about doing this?
Thanks
Make a borderless window, the size of the menu-bar screen (screen 0—not [NSScreen mainScreen]), positioned at 0,0, with window level kCGDesktopWindowLevel.
Remember that you will need to observe for screen frame-change notifications (when the user changes the screen dimensions), and that you should correctly handle the case of no screen at all (headless Mac).
I think #Peter Hosey’s solution should work, but to make other windows go on top, you will probably need to change the window level to something else.
But, I implore you, do not do this. This will be the most bugly application the Macintosh has ever seen. There are a lot of really good user interface paradigms that you can use, and "replicating" the main desktop interface of Mac OS X is generally not one of them. That is, unless you are reimplementing Time Machine or something like that.