Camera view controller segues

Hi,
I have a question about adding a camera and photo editing component into an app, and think I have a general idea on how to achieve this but need some insight on whether I am thinking the right way. I want to capture a photo with an AVCaptureSession and present that photo in a UIImageView throughout a series of viewcontrollers for editing purposes (crop, to add caption, to submit to live feed etc...). I am thinking the way this would be acheived is to present each view controller for the capture and editing process modally, but what I am having trouble with is passing the captured image to the next view controller...what are the methods for taking the captured image and then moving it to the next view controller which presents the captured image...from what I have researched I would be using presentingViewControllers and presentedViewController methods...correct? Would I use a prepareForSegue method that once camera captures an image the following view controller is presented...?
Essentially the segue process would be very similar to instagrams camera viewcontrollers replacing the filters with cropping the photo. But for now all I want to confirm / figure out is how to pass the image from view controller to view controller.
Thank you very much for any feed back.

Hi Ian,
Create a component controller method check_mandatory_fields
The following should the parameter interface of the method.
I_VIEW_CONTROLLER     Importing     Type ref to IF_WD_VIEW_CONTROLLER
In this method, call cl_wd_dynamic_tool=>check_mandatory_attr_on_view to do the validation.
In main view, when you want to validate the records, do the following.
DATA: lo_view_controller TYPE REF TO if_wd_view_controller.
lo_view_controller ?= wd_this->wd_get_api( ).
wd_comp_controller->check_mandatory_fields(
    EXPORTING
      i_view_controller = lo_view_controller ).
These validation can be done at view level. So in detaild view, when you want to validate do the same as mentioned above.
Regards,
Sravan varagani

Similar Messages

Replacement of detail view controller using segues

Im trying to get a button in the master view controller of a UISplitView controller to change the image being shown in the detail view controller of the same UISplitView controller. Im trying to find out if it is possible to do this with segues alone without defining IBActions. If so, Im having trouble figure out what kind of segue would do this. I tried to control-drag from the button in the master view controller to the instance of the detail view controller that I want replacing the first instance(root instance) of the detail view controller and choosing the replace segue but that isn't working out. Any help would be greatly appreciated. I found this was easier to do in the UINavigationController using storyboard and segues because you just "draw" the different instances with different images on the IB canvas and they get pushed according to what button you pressed in the previously on screen view controller however Im having trouble doing this in a split view controller's detail side which in my case is not inside a UINavigationController.

Hi Lakshmi,
Doing with MVC would be simpler one compared to page with flow logic.
Lakshmi you have specified that u have created HEADER IN ONE VIEW and the buttons needed foe the same page in another view.
You can replace that by including the coding as follows.
Write the codings needed for header in page fragment and include that in the needed page using the syntax
<%@ include file="relative URL"%> relative url is the name of the fragment under which you have to write the coding for header.
Once you have done this you can include the header in any view just by calling the above syntax alone.
After the completion of this task,you can design the buttons in the same view in which you have included the header.Time consumption will be advantage here.
You have specified that, by clicking a button your page should be navigated to second and so on.This can be easily achieved by pressing the following keys under DOHANDLEEVENT.
case evevt.
when 'id of button 1'
navigation ->next_page('*goto'*)
Follow thew same for all the buttons in their respective DOHANDLEEVENT
In the main page(ie by clickin the name of the application you will bw getting a window) in you should specify as
firstpage.htm goto secondpage.htm
Link:[helplink|http://help.sap.com/saphelp_nw04/helpdata/en/28/4bae407e69bc4ee10000000a1550b0/framese
t.htm]
Hope this will help you.
With Regards,
SHARMILA BRINDHA.M

How to go from a View Controller to a View Controller

Hey everyone, I have asked this question over on Stack Overflow, and really had no luck with it.
     I am wondering how to go from one (1) View Controller that has buttons and another View Controller that has a UIWebViewer in? I know how to do the simple part to get the two to link up. But, the buttons are going to have different URL's hooked up to them, and I want to be able to reuse the Web Viewer. I am using the Swift Programming language to be able to do this.
below is my current code that is has my buttons sitting on top of my web viewer,
import UIKit
import WebKit
class ViewController: UIViewController {
    @IBOutlet var wbView: UIWebView!
    var strUrl = ""
        @IBAction func buttonAction(sender: UIButton) {
            switch (sender.tag){
            case 1:
                strUrl = "https://www.google.co.in/"
            case 2:
                strUrl = "https://in.yahoo.com/"
            case 3:
                strUrl = "https://www.facebook.com/"
            case 4:
                strUrl = "https://bing.com/"
            default:
                break;
            reloadWebViewWithUrl(strUrl);
        func reloadWebViewWithUrl(strUrl: NSString){
            var url = NSURL(string: strUrl);
            var request = NSURLRequest(URL: url!);
            wbView.loadRequest(request);
        override func viewDidLoad() {
            super.viewDidLoad()
            // Do any additional setup after loading the view, typically from a nib.
        override func didReceiveMemoryWarning() {
            super.didReceiveMemoryWarning()
            // Dispose of any resources that can be recreated.
How should I go about changing this two allow my buttons to be in their own ViewController and still be able to to the secondary View Controller with the WebViewer?
Thank You all in advanced with the help on this!

This is the FirstViewController Code
import UIKit
class FirstViewController: UIViewController {
    @IBAction func webAction(sender: UIButton) {
        let index = sender.tag
        chosenURLString = addresses[index]
        performSegueWithIdentifier("WebViewSegue", sender: self)
    override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?) {
        if let controller = segue.destinationViewController as?
            SecondViewController {
            controller.urlString = chosenURLString
            chosenURLString = nil
    private let addresses = ["", "https://www.google.com", "https://www.facebook.com", "https://spca.org", "https://www.facebook.com/wagzpack?fref=photo"]
    private var chosenURLString: String?
This is the SecondViewController Code
import UIKit
class SecondViewController: UIViewController {
    @IBOutlet var webSite: UIWebView!
    var urlString: String?
    override func viewDidLoad() {
        super.viewDidLoad()
        if let urlString = urlString {
            if let url = NSURL(string: urlString) {
                let request = NSURLRequest(URL: url)
                webSite.loadRequest(request)
                println("loading \(urlString)")
            else {
                println("badly formed URL string.")
        else {
            println("missing URL string.")

Update methode in model-view-controller-pattern doesn't work!

I'm writing a program in Java which contains several classes. It must be possible to produce an array random which contains Human-objects and the Humans all have a date. In the program it must be possible to set the length of the array (the number of humans to be produced) and the age of the humans. In Dutch you can see this where is written: Aantal mensen (amount of humans) and 'Maximum leeftijd' (Maximum age). Here you can find an image of the graphical user interface: http://1.bp.blogspot.com/_-b63cYMGvdM/SUb2Y62xRWI/AAAAAAAAB1A/05RLjfzUMXI/s1600-h/straightselectiondemo.JPG
The problem I get is that use the model-view-controller-pattern. So I have a model which contains several methodes and this is written in a class which inherits form Observable. One methode is observed and this method is called 'produceerRandomArray()' (This means: produce random array). This method contains the following code:
public void produceerMensArray() throws NegativeValueException{
     this.modelmens = Mens.getRandomMensen(this.getAantalMensen(), this.getOuderdom());
for (int i = 0; i < this.modelmens.length; i++) {
          System.out.println(this.modelmens.toString());
this.setChanged();
this.notifyObservers();
Notice the methods setChanged() and notifyObservers. In the MVC-patterns, these methods are used because they keep an eye on what's happening in this class. If this method is called, the Observers will notice it.
So I have a button with the text 'Genereer' as you can see on the image. If you click on the button it should generate at random an array. I wrote a controller with the following code:
package kristofvanhooymissen.sorteren;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
/**Klasse GenereerListener.
* @author Kristof Van Hooymissen
public class GenereerController implements ActionListener {
     protected StraightSelectionModel model;
     /**Constructor.
     *@param model Een instantie van het model wordt aan de constructor meegegeven.
     public GenereerController(StraightSelectionModel model) {
          this.model = model;
     /**Methode uit de interface ActionListener.
     * Bevat code om de toepassing te sluiten.
     public void actionPerformed(ActionEvent arg0) {
     this.model=new StraightSelectionModel();
     try{
     this.model.produceerMensArray();
     } catch (NegativeValueException e){
          System.out.println("U gaf een negatieve waarde in!");
     this.model.setAantalMensen((Integer)NumberSpinnerPanel.mensen.getValue());
     this.model.setOuderdom((Integer)NumberSpinnerPanel.leeftijd.getValue());
StraighSelectionModel is of course my model class. Nevermind the methods setAantalMensen and setOuderdom. They are used to set the length of the array of human-objects and their age.
Okay. If I click the button my observers will notice it because of the setChanged and notifyObservers-methods. An update-methode in a class which implements Observer.
This method contains the follow code:
public void update(Observable arg0,Object arg1){
          System.out.println("Update-methode");
          Mens[] temp=this.model.getMensArray();
          for (int i = 0; i < temp.length; i++) {
               OnbehandeldeLijst.setTextArea(temp[i].toString()+"\n");
This method should get the method out of the model-class, because the produceerRandomArray()-methode which has been called by clicking on the button will save the produce array in the model-class. The method getMensArray will put it back here in the object named temp which is an array of Mens-objects (Human-objects). Then aftwards the array should be put in the textarea of the unsorted list as you could see left on the screen on the image.
Notice that in the beginning of this method there is a System.out.println-command to print to the screen as a test that the update-method has been called.
The problem is that this update method won't work. My Observable class should notice that something happened with the setChanged() and notifyObservers()-methods, and after this the update class in the classes which implement Observer should me executed. But nothing happenens. My controllers works, the method in the model (produceerRandomArray() -- produce random array) has been executed, but my update-method won't work.
Does anyone has an explanation for this? I have to get this done for my exam an the 5th of january, so everything that could help me would be nice.
Thanks a lot,
Kristo

This was driving me nuts, I put in a larger SSD today going from a 120GB to a 240GB and blew away my Windows Partition to make the process easier to expand OS X, etc. After installing windows again the only thing in device manager that wouldn't load was the Bluetooh USB Host Controller. Tried every package in Bootcamp for version 4.0.4033 and 5.0.5033 and no luck.
Finally came across this site:
http://ron.dotsch.org/2011/11/how-to-get-bluetooth-to-work-in-parallels-windows- 7-64-bit-and-os-x-10-7-lion/
1) Basically Right click the Device in Device manager, Go to Properties, Select Details tab, Choose Hardware ids from Property Drop down.   Copy the shortest Value, his was USB\VID_05AC&PID_8218
2) Find your bootcamp drivers and under bootcamp/drivers/apple/x64 copy AppleBluetoothInstaller64 to a folder on your desktop and unzip it. I use winrar to Extract to the same folder.
3) Find the files that got extracted/unzipped and open the file with notepad called AppleBT64.inf
4) Look for the following lines:
; for Windows 7 only
[Apple.NTamd64.6.1]
; No action
; OS will load in-box driver.
Get rid of the last two lines the following:
; No action
; OS will load in-box driver.
And add this line, paste your numbers in you got earlier for USB\VID_05ac&PID_8218:
Apple Built-in Bluetooth=AppleBt, USB\VID_05ac&PID_8218
So in the end it should look like the following:
; for Windows 7 only
[Apple.NTamd64.6.1]
Apple Built-in Bluetooth=AppleBt, USB\VID_05ac&PID_8218
5) Save the changes
6) Select Update the driver for the Bluetooth device in device manager and point it to the folder with the extracted/unzipped files and it should install the Bluetooth drivers then.
Updated:
Just found this link as well that does the same thing:
http://kb.parallels.com/en/113274

I have a swipe gesture that swipes a UIView onto the main View Controller. Is there a way to change the speed that the UIView swipes on?

I dont need the image to swipe to follow the speed of the gesture, I just want the swipe to be slower as at the moment it comes on so fast it almost pops on.
Thanks!

Thank you very much for your speedy answer.
I was hoping to get the effect of a push segue from the initial View Controller screen to a UIView on that same view controller. I seem to be able to add this option into my Swipe Gesture connections, (storyboard shows the segue arrow exiting the View controller and then pointing back into the same View Controller) This would be ideal, but I cant work out if its possible to link this segue to the new UIView I want. At the moment it just feeds back to the initial View Controller screen! Argggh!!!

How to fire event in view controller from component controller.

I have a component usage that fires an event wich i have subscribed in the component controller.
iv_usage->subscribe_event( iv_event_name = 'TAKE_IT'
iv_handler = me ).
After the event the method IF_BSP_WD_EVENT_HANDLER~HANDLE_EVENT in the component controller is called.
method if_bsp_wd_event_handler~handle_event.
endmethod.
The usage component is opened as a popup window. After pressing a button, the data is transfered via context node binding to the calling component. But now i want to close the popup.
My intension is to fire a event for the view controller in the IF_BSP_WD_EVENT_HANDLER~HANDLE_EVENT method that closes the popup.
Is this possible?
Or let me explain it this way:
I want to close a popup after a button in the popup is pressed.
best regards
Jürgen

Hello Juergen
I am assuming your target pop-up is of type ref to IF_BSP_WD_POPUP.
1.Make this a view controller class attribute.
2. After the code to create the pop-up, you can add the following block :
gv_target_popup->set_on_close_event( iv_view = me iv_event_name = 'CLOSEPOPUP').
3. Now define event handler EH_ONCLOSEPOPUP where you can write the logic for on_close.
You can access the same reference gv_target_popup at the event handler level as well.
Hope this helps.
Regards
Nisha

My camera always freezes when I try to switch to front camera view. How can I fix this?

The original camera app on my iPod touch does not work. The camera shutter would not open. I purchased and downloaded another camera app and it works- only the camera freezes when Itouch the icon in top left corner to get it to switch to front camera view. Has anyone had this problem? If so is there something I can do to correct it?

Have you tied the standard fixes:
- Reset:
Reset iPod touch: Press and hold the On/Off Sleep/Wake button and the Home
button at the same time for at least ten seconds, until the Apple logo appears.
-restore the iPod from backup
- Restore the iPod to factory defaults.
- Also look at this long-running previous discussion on your problem.
Camera shutter issue: Apple Support Communities

How to get the VIEW_ID from VIEW Controller Class?

Hi,
In my BADI(CRM_BP_UIU_VIEW_CONFIG), I have a view controller variable(IR_VIEW_CONTROLLER) referring to CL_BSP_WD_VIEW_CONTROLLER. Now, I have to get VIEW_ID using this varibale. However, the VIEW_ID attribute is Protected in the class .CL_BSP_WD_VIEW_CONTROLLER So, I am unable to access this attribute.
Could you please help me out, how can I do achieve this?
Thanks,
Sandeep

See if you can make use of GET_VIEWAREA_CONTENT or GET_VIEWAREA_CONTENT_ID...
Regards,
BJ

Call method with an argument from another view controller

I have a UIViewController MainViewController that brings up a modal view that is of the class AddPlayerViewController. When the user clicks 'Save' in the modal view I need to pass the Player data (which is a Player class) from the modal view to the MainViewController in addition to triggering a method in the MainViewController. What's the best way to accomplish this? I'm new to cocoa and have only tried using delegates and some ugly hacks to no avail.
Thanks for the help.

If I understand correctly, you have:
1. A model object, Player.
2. A top view controller, MainViewController.
3. Another view controller, AddPlayerViewController, which MainViewController displays modally.
I'm guessing that AddPlayerViewController creates a new Player object and lets the user set its values, and you need a way to get that new Player into MainViewController once they're done.
So, here's what I'd do:
1. Create an AddPlayerViewControllerDelegate protocol. It should declare two methods, "- (void)addPlayerViewController:(AddPlayerViewContrller*)controller didAddPlayer:(Player*)newPlayer" and "- (void)addPlayerViewControllerNotAddingPlayer:(AddPlayerViewController*)controll er".
2. Add an attribute of type "id <AddPlayerViewControllerDelegate>" called delegate to AddPlayerViewController. Also add a property with "@property (assign)" and "@synthesize".
3. Modify AddPlayerViewController so that if you click the "Save" button, addPlayerViewController:didAddPlayer: gets called, passing "self" and the new Player object as the two arguments. Also arrange for clicking the "Cancel" button to call addPlayerViewControllerNotAddingPlayer:.
4. Modify MainViewController to declare that it conforms to AddPlayerViewControllerDelegate. Implement those two methods (addPlayerViewControllerNotAddingPlayer: might be an empty method if you don't want to do anything).
5. When you create your AddPlayerViewController, set its delegate to your MainViewController.
If you need more detail, let me know what parts you need me to elaborate on.

Question about view/controller/nib class design

Assume you need to make an application with, let's say, 15 different views in total. There are two extreme design choices you can use to implement the app:
1) Every single view has its own view controller and a nib file. Thus you end up with 15 controller classes and 15 nib files (and possibly a bunch of view classes if any of your views needs to be somehow specialized).
2) You have only one controller which manages all the views, and one nib file from which they are loaded.
AFAIK Apple and many books recommend going purely with option #1. However, going with this often results in needless complexity, large amounts of classes (and nib files) to be managed and complicated class dependencies, especially if some of the views (and thus their controllers) interact with each other or share something (something which would be greatly simplified if all these related views were handled by one single controller class).
Option #2 also usually ends up being very complex. The major problem is that the single controller will often end up being enormous, handling tons of different (and usually unrelated) things (which is just outright bad design). This is seldom a good design, unless your application consists of only a few views which are closely related to each other (and thus it makes sense for one single controller class to handle them).
(Option #2 also breaks the strictest interpretation of the MVC pattern, but that's not really something I'm concerned about. I'm concerned about simple design, not about following a programming pattern to the letter.)
A design somewhere in between the two extremes often seems to be the best approach. However, since I don't have decades of Cocoa programming experience, I would like to hear some opinions about this subject matter from people with more experience on that subject. (I do have object-oriented programming experience, but I have only relatively recently started programming for the iPhone and thus Cocoa and its design patterns are relatively new to me, so I'm still learning.)

Somehow I get the feeling that my question was slightly misunderstood.
I was not asking "which one of these two designs do you think is better, option #1 or option #2?" I already said in my original post that option #2 is bad design (unless your application consists of just one or two views). That's not the issue.
The issue is that from my own experience trying to adhere very strictly to the "every single view must have its own view controller and nib file" often results in needless complexity. Of course this is not always the case, but sometimes you end up having controller classes which perform very similar, if not even the exact same actions, resulting in code repetition. (An OO'ish solution to this problem would be to have a common base class for these view controllers where the common functionality has been grouped, but this often just adds to the overall complexity of the class hierarchy rather than alleviating it.)
As an example, let's assume that you have a set of help screens (for example one help screen for each major feature of the app) and a view where you can select which help view to show. Every one of these views has, for example, a button to immediately exit the help system. If you had one single controller class managing these views, this becomes simpler: The controller can switch between any of the views and the buttons of each view (most of them doing the same things) can call back actions on this controller (eg. to return to the help selection or to exit the help screen completely). These help screens don't necessarily have any functionality of their own, so it's questionable what do they would need view controllers of their own. These view controllers would basically be empty because there's nothing special for them to do.
View controllers might make it easy to use the navigation controller class, but the navigation controller is suitable mainly for utility apps but often not for things like games. (And if you need animated transitions between views, that can be implemented using the UIView animation features.)
I also have hard time seeing the advantages of adhering strictly to the MVC pattern. The MVC pattern is useful in things like web servers, where MVC adds flexibility. The controller acts as a mediator between the database and the user interface, and it does so in such an abstract way that either one can be easily changed (eg. the "view", which normally outputs HTML, could be easily changed to a different "view" which outputs a PDF or even plain text, all this without having to touch the controller or the model at all). However, I'm not seeing the advantages of the MVC pattern in an iPhone app. It provides a type of class design, but why is it better than some other class design? It's not like the input and output formats of the app need to be changed on the fly (which is one advantage of a well-designed program using the MVC pattern).

I'm trying to import some Hi8 into FCPX via a Canon GL2. Although the footage shows up in the import window, it says "Camera not controllable". The manual import button does activate, but footage is not actually being imported. Any ideas? Thanks

I'm trying to import Hi8 into FCPX via a Canon GL2. Although the footage appears in the import window, it says camera not controllable. The manual import buttons activate, but the footage is not actually importing. Any ideas? Thanks so much.

What Tom said.
Or you may be able to import using a different program - try with Quicktime Player, "New Movie Recording". If the camera appears as an option, it should work.

TP CONFIGURATION PROBLEM ( While creating a View Controller in Component )

Hi All,
     I have a problem in TP Config while creating a View Controller in a component i am getting this Exception
    Parameter lsm(&1) not in version 0004(&2) of tp configuration .
    This Exception Raised from this Function Module : RS_ACCESS_PERMISSION
Any on can please help me to come out of this issue.
Regards And Thank you,
Nirmala.K

Sounds like you should be using one of the Apps forums, perhaps {forum:id=210}

Hook methods in component controller vs hook methods in view controller

Hi,
I want to know how WDDoInit in component controller differs from the same in view controller.
How the lifecycle flows in both controllers?
Eg. if i create a method intialize() in both component & view controllers and if i called initalize method in view, which one will be called?
Need to know how the flow works.
Regards,
Manoj

Dear Manoj,
Please check if it is helpful.
The order of execution of standard hook methods when a WDJ application is called the first time is as follows:
1. Component Controller DoInIt()
2. View Controller DoInIt()
3. Interface Window Controller
4. Component Controller DoBeforeNavigation()
5. Component Controller DoModify()
6. Component Controller DoPostProcessing()
After this, if you navigate to some other view, then the order of execution of methods of that New view will be:
1. Component Controller DoBeforeNavigation()
2. New View DoInIt()
3. New View onPlugfromFirstView
4. Component Controller DoModify()
5. Component Controller DoPostProcessing()
Then, if you again navigate back to the first view, then the order of execution of methods is:
1. Component Controller DoBeforeNavigation()
2. New View onPlugfromNewView
3. Component Controller DoModify()
4. Component Controller DoPostProcessing()
Webdynpro - Sequence of Execution
Thanks & Regards,
Patralekha

Diff between Component controller,Custome controller and View controller

hi,
Can any body tell me the following details,
1.difference between the Component controller,Custome controller and View controller in WD-ABAP.?
2.what is Lead Selection?
Regards,
Ravi

Hi Ravi.
The component controller is visbile to all views in a component. So all context nodes and methods you create here can be accessed from all views in the component. This way you can share data between the views by mapping context nodes or thru method calls. You can also mark methods and nodes as interface so that they are acessable from other components that define component usages to this cmponent.
Custom controller is quiet similar to the component controller. You can define it if you want to group some views with a custom controller for a certain functionality.
If you want to access a custom controller in a view you have to define the usage first on the properties tab of the view.
A view controller is only visible in the view itself. So all methods or context nodes you define here are only accesable by the current view.
The lead selection is in most cases the current selected element in a context node. The lead selection is used by many UI elements to determine which element has to be shown (e.g drop down).
If you have a table with single selection the current selected table row is the lead selection element of the bound context node.
SO you can get the lead selection element easily in any mthod by calling context_node->get_element( ).
Hope this clears your questions.
Cheers,
Sascha

IC WebClient - Lifetime of a view controller

Hi,
The cookbook states:
<i>When the user navigates to a new view and the previous view is no longer visible, both the controller and the view are destroyed (removed from memory).</i>
Hence, I thought the method 'Constructor' of the class will be called every time the user navigates back to that view, but it does not seem the case. This method is called only first time the view is accessed.
If the controller class is destroyed wouldn't the Constructor need to be called every time to re-create the object ?
Am I missing out something ?
Mihai

Hi Mihai,
yes you are missing the concept of custom controller.
the life time of the view controller is as long as the view is displayed. whenever that view is replaced with another view the controller will get distroyed!.
But you can keep the data ( context node ) alive by linking the node with a custom controller node, which have life time until the entire application runs.
Regards,
sudeep v d.

Camera view controller segues

Similar Messages

Maybe you are looking for