I would like to know if it is possible to turn on the sony camera dsc-qx100 (or qx10) programmatically or if it is mandatory to turn it on manually ?
Also, is it possible to control the period before the camera turns off ?
My idea is to be able to switch between two cameras and it seems that if I don't connect to one for a while, it will turning off automatically (My test on playMemories app gives me four minutes before it turns off).
Is there a way to avoid that ?
Thanks
Controlling the power state is not possible programatically.
This is not controllable either.
(My test on playMemories app gives me four minutes before it turns
off). Is there a way to avoid that ?
On some models it is possible to programmatically change autoPowerOff time or to deactivate it. Look for setAutoPowerOff.
Related
How I can set auto-ISO by Sony Remote Camera API?
I'm able to set any specific value, but what about "auto"? Since PlayMemories-Home app does it, there is a way, but it's not documented.
Thanks,
Oleg.
Did you check/get 'available' (vs 'supported') values? Sometimes I have seen that some values are only usable if the camera is in a particular mode.
You might try changing the shooting mode and see if that then allows you to change ISO setting to auto.
Cheers,
Simon
Before Windows Universal, if I wanted to prevent the screen from turning off, I could use:
PhoneApplicationService.Current.UserIdleDetectionMode = IdleDetectionMode.Disabled;
That API is now gone and I can't find anything like it. Can someone help me find the right way to do this now?
Take a look at DisplayRequest class: https://msdn.microsoft.com/en-us/library/windows/apps/br241816.aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-2. It's intended to apps which
show video or run for extended periods without user input
so it should be a solution.
I've got a terminal application that needs to take a webcam picture and then perform some processing on it. I'm having trouble getting it to initialize. There's a fairly complete demo with an app called MyRecorder in the Apple docs that uses QTKit, which I was able to make work fine. I was also able to modify it to grab a single frame instead of a stream.
When I move this to a terminal application, the startRunning of the QTCaptureSession command simply does nothing. There are no errors, and everything reports as successful, but my webcam doesn't light up, and no frames are captured.
Any idea what's going on here? Are there any kind of security restrictions, or other kinds of restrictions that would prevent the QTCaptureSession from working?
So switching to AVFoundation solved my problem. I'm still not certain what the issue is, but for now using AVFoundation seems like the way to go since it was designed to replace QtKit anyways.
Is there any way in which the usage of the camera of the iPad2 can be restricted only to my application? even if it is using i tunes.
could not find any code related to it. some code would be helpful.
There's no way to achieve this. I think it could be done with quite a bunch of hacking if you were developing for Cydia, but I'm not sure ever then. If the user quits your application or switches from it, the system will make the camera available to any other app requesting it.
I want to develop a screensaver-like app where the only way of getting back to the springboard is entering a code. Therefore I would need the Home Button action to be ignored, that is that when the user presses the button nothing happens..or something custom...instead of going back to the springboard and terminating the app.
Is this possible? does anybody know if apple will approve/reject this kind of app?
The answer to your question is, yes.
The answer to the question you meant to ask--can I ship an app through the iPhone store that has the home button disabled--is no.
If you are only publishing your app to jailbroken phones you can do it, but it will piss everyone off.
Edit 7 years later:
This is actually extremely possible now--there is a standard feature in the iPhone called "Guided Access". It's hidden under that "Accessibility" Link (With some other fairly cool stuff like flashing the LED whenever you get a call and allowing a Bluetooth keyboard to tab between controls)
It's called "Guided Access". You set a passcode, launch the app then triple-click the home button to start guided access.
It disables exit and allows you to designate regions of the screen you can't touch. You can also set a time limit (For kids playing which seems to be the reason a lot of people look up this question).
Tempted to edit the "Accepted answer" and throw this info in there, but that seems rude so I'll just hope people find this answer.
Annoyingly you also seem to be unable to shut off the phone--I suppose this is perfect for people who want their kids to play a game, but might not hit the original asker's problem of restricting access to a single app (I mean it WILL do that but it'll also prevent it from doing ANYTHING else).
Not with public APIS (and hopefully, not with private ones). Even if you manage it somehow, Apple will reject it for breaking UI guidelines. Moreover, even if they didn't, people could always use the iPhone's "Force Quit" equivalent to hard terminate your app.
Apple is not going to approve this type of app, they state pretty explicitly that you're app needs to respond appropriately to springboard telling the app to terminate both when things like phone calls come in and when memory warnings come in.
This is not possible with the current SDK, nor do I suspect it will ever be.
You might be able to get this behaviour via jailbreaking, but you won't be able to sell your app through iTunes, nor will Apple ever approve such an application.
You can do it like this
Install the following mobileconfig file
This will disable the home button once you launch the app
Download
Found the link Here
Apple won't allow it.
What if something emergency happens and you wan to dial an emergency phone number. You are putting the user at risk. The trade-off isn't worth it.