I have an existing application developed for Windows Phone 7, which uses CameraCaptureTask.
The captured image is returned back to the app, which will be processed for grayscale conversion.
While testing the same app (same binary to be precise) in Windows Phone 8 Lumia 920, I figured that a copy of all the images captured through the CameraCaptureTask are saved in "camera roll" folder.
This is a bit annoying as the users of my app are not expecting the captured images crowding the "camera roll" folder. I looked up the documentation http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh394006(v=vs.105).aspx and found the below quote,
On Windows Phone 8, if the user accepts a photo taken with the camera capture task, the photo is automatically saved to the phone’s camera roll. On previous versions of Windows Phone, the photo is not automatically saved.
So far I couldn't find a way to avoid this case in Windows Phone 8.
Is there a way to turn off this feature before calling the CameraCaptureTask's Show() method in Windows Phone 8?
No. This is a consumer feature request implemented on WP8 that's transparent to developers. The usecase here is that a consumer uses the CameraCaptureTask to line up a perfect shot, doesn't use it an app for whatever reason and can't find it ever again later.
As a side-note, I actually had this happen a few times to me when using various twitter and photo editing apps and it's quite annoying.
Makes no sense. CameraCaptureTask was created to allow apps to capture photos for the app use, not for users to push them into Camera Roll. That is what Lenses are for (either custom code can write into camera roll as well).
It is not transparent to developers because one of my apps has just been removed from the WP8 market. They say because can cause "undesired upload of an app photo to skydrive".
Justin are you sure it isn't a bug? is it going to be fixed?
This forces me to break my development into 2 now: WP7 and WP8. I don't want that hassle right now...
Related
Google play console wants me to add some 7-inch tablet screenshots in order to make the app easily accessible to tablets. But I don't have any tablet. Don't understand what's the problem. I have made screenshots in the final phase of development, testing the game in the Unity editor. I suppose these .png images are as good as if they were made from a phone. I don't even know how to make screenshots from a phone.
Is there a hidden feature to identify a screenshot as being made from the 7-inch tablet? Why don't they simply state the image resolution they want for the tablet "screenshot"??
Actually, it doesn't matter what resolution your image is. Just upload the images to that section, the purpose of that section is only to let your users have a first look of what your app looks like before they install it. If you don't intend to make your app for Tablet, just let that section empty, upload images only to Phone's section.
If you are using an Android phone such as Samsung, I would recommend you have a look at Settings/Advanced Features/ Smart Capture (turn it on). Then you can swipe your screen to take a screenshots (it has a tutorial there)
I'm trying to do something very simple: implement a program that activates the back camera of my WP8 device. Could anyone help me do that?
If so you could try using the PhotoCamera class in order to capture images. I'm not pretty sure whether you'll be able to open the native Camera app of the device.
References:
How to access the camera from my Windows Phone 8 app (XAML and C#) and save the taken picture in a determined folder?
Sample from MSDN
Minimal Camera app in Windows Phone
I am working on a Windows 8.1 store game.
There is no specific need for the game to be a windows store app but I use it for development since I already had code for windows store and didn't bother to migrate the input and game loop code to a traditional desktop app.
The issue I am having now is that the Pointer(which can be a mouse/touch/pen) is bound to the screen's resolution.
I didn't find any way to work around it or to set the mouse cursor so I can't create a first person shooter like aimer or pointer.
I know it is possible to do so in a traditional win32 desktop app but I wonder if this limitation is only for Windows Store apps or will I encounter the same limitation in a traditional desktop app that runs on Windows 8.1?
In other words is this limitation a Windows 8.1 thing? Or a Windows store app thing?
Is there a way to create a FPS like mouse/aimer in a windows 8.1 store app?
You can remove the app window bounds limitations and it is possibly even easier than in a Win32 app. The only thing you need to do is this:
Window.Current.CoreWindow.PointerCursor = null;
From now on handle this event to get the delta values when the mouse moves:
MouseDevice.GetForCurrentView().MouseMoved
I use it here.
I have a Windows Phone app that targets OS 7.1 and I wish to be available for Windows Phone 8 devices as well. As I understand it I needn't do anything code-wise to make this possible. However, must I add new tile images to get it certified? According to App submission requirements for Windows Phone the XAP must include more images for Windows Phone 8 than for Windows Phone 7 (see Default Tile images under section 4.7.2), is this the case here or does it only apply to Windows Phone apps targeting OS 8.0 and higher?
I did not get your question what actually you want? but if you want to upload your .xap in app store than you have require
300x300 app icon
1000x800 back ground image
If your application support multiresolution than six WXGV(768x1280) screen shots else you need six single resolution screen shots
If you are talking about application icon than visit bellow link you got every thing
Tile size and resolution
Tile design Guideline
Multi resolution for windows phone
good. to know the requirements of your app or the window phone 8, i can assume you have been using Visual Studio 2010. i have had a similar experiance to one of my apps. i simply opened my project.snl file with visual studio 2012 and at the AppManifest page, i was able to add the stuffs (images for toast, tile and other images required which i provided in various sizes). you'll also have the advantage of adding some more cool features like a better arrangement of your app which you switch the orientation.
your app will still perform good on window phone 7 series too.
i hope this helps.
Your app is already available as is for WP8 devices.
That's not clear what do you mean by images.
If you are talking about screenshots for Marketplace:
If you have a separate XAP you'll have to add screenshots to it.
Nowadays it's enough to add a set of screenshots in WXGA (1280 x 768) resolution.
If you are talking about icons and other images you use inside the app:
you should add images in WXGA (1280 x 768) resolution. They will be resized to all supported screen resolutions.
WP8 app should contain 99 x 99 pixel PNG image as app list image and at least two main tile images: small and middle one. Wide tile is up to you.
To supppoert all tile sizes you will need to include the tile images for that size. If you don't, your app will still work, but the tile for your app couldn't be resized.
I am developing a security related windows phone application. I need to disable/block screen capture for my application.
In Android, we used to set a flag FLAG_SECURE to the window of which we want to block the screen capture. Is there anything similar in wp7 also??
Thanks
You can't do screen captures on Windows Phone unless you use homebrew apps, so I wouldn't worry too much about it.
And even if there were screen capture apps on the marketplace, you would have no way to be safe. Even if you found a way to prevent screen captures, how would you prevent users from taking a picture of the phone with a camera, or sideloading the app on the emulator then making screen captures of the emulator?
There's currently no API available to developers that allows you to perform screen captures with a locked device.
The alternatives are as follows:
Unlock your device and sideload one of the homebrew based screen
capture apps.
Take a picture of the screen itself (Crude but it
would do the job).
Microsoft have stated that they do not intend to change this in the near future (CNET Article)