Switching view controller crashes

I set a button to change the view controller and i get this error please help

hey!!!!! that happened to my (brand new - never been serviced/fixed) iPod too!! the only problem was, the cick wheel also stopped responding ... grrr
i took my iPod to an AppleCentre - they told me that they would try to fix it but if they couldnt they would send a replacement - now you say they do a crap job at fixing them i hope i get a new one!

Similar Messages

SPD 2013 WorkFlow starts in visual mode and crashes when publishing or switching views

When editing a Workflow in SPD 2013, the WF forces the WF to open in visual mode and I am unable to publish or change the view without crashing SPD. When any action is taken on this
workflow a progress bar flashes and "Exporting Workflow" is displayed -- this process either crashes SPD or locks the computer.
I have completed the following
without success:
uninstalled & reinstalled SPD and Visio (32 bit),
cleared caches,
uninstalled and reinstalled SPD and Visio to 64 bit,
installed all updates
Any guidance is much appreciated.

Hi,
Could you test the issue on another machine with both Visio and Designer installed?
Does the issue occur to all workflows?
I find similar issue for your reference:
https://premierpointsolutionstraining.wordpress.com/2014/01/24/sharepoint-designer-crashes-workflow-design-view/
http://answers.microsoft.com/en-us/office/forum/office_2013_release-visio/visio-2013-sharepoint-designer-2013-crash/424c5720-2ae0-404c-9a53-2a06cddd3365?auth=1
Please test if updates matters in your situation.
Regards,
Rebecca Tu
TechNet Community Support

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).

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.")

Autorotate stops when switching view from popover

Hi guys. This is my first post here (on my first iOS app) so please be gentle
I have my iPad app set to Autorotate between both right and left home button landscape modes.
Everything seams to be working fine when i build and run. Auto rotation works and only admit landscape modes.
In my view controller i have a button linked to a popover with 4 other buttons to swich to 4 different views.
When i switch to any of those other views autorotation stops working.
All those views have the same code to accept autorotation:
- (BOOL) shouldAutorotateToInterfaceOrientation: (UIInterfaceOrientation) interfaceOrientation {
return (interfaceOrientation == UIInterfaceOrientationLandscapeRight || interfaceOrientation == UIInterfaceOrientationLandscapeLeft);
The popover also has that code and is displaying the buttons in the correct way when I rotate the screen. I assume that the popover is autoratating fine, but the rest of the view stays upside down.
I'm switching views from the popover with the following code:
- (IBAction)GotoView02{
View02ViewController *View02 = [[View02ViewController alloc] initWithNibName:nil bundle:nil];
[self presentModalViewController:View02 animated:NO];
Any ideas why autorotation stops working?

Same problem here, happening both in the simulator and on the device itself.
Have you found a solution yet?

Loading a View Controller based on UITableViewController cell

Hi,
I've been trying to make my TableViewController cells load different UIViewControllers when they are clicked, but haven't been having any luck. All that happens is my program starts but then when I click on the cells, the view freezes. This is my code for just loading one view but this can easily be changed to load different views later:
- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath {
UIViewController *targetViewController = [menuList objectAtIndex: indexPath.row];
if (targetViewController == nil) {
switch(indexPath.row){
case 0: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
case 1: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
case 2: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
case 3: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
targetViewController = [menuList objectAtIndex: indexPath.row];
[[self navigationController] pushViewController:targetViewController animated:YES];
is there a better way of doing this? I tried if(indexPath.row == 0) but that seemed to make it freeze as well!

// MyTableController.h
#import <UIKit/UIKit.h>
#define kMenuLabelTag 100
@interface MyTableController : UIViewController <UITableViewDelegate, UITableViewDataSource> {
IBOutlet UITableView *myTableView;
NSArray *menuList;
NSMutableArray *controlList;
IBOutlet UINavigationController *navigationController;
@property (nonatomic, retain) IBOutlet UITableView *myTableView;
@property (nonatomic, copy) NSArray *menuList;
@property (nonatomic, retain) NSMutableArray *controlList;
@property (nonatomic, assign) IBOutlet UINavigationController *navigationController;
@end
// MyTableController.m
#import "MyTableController.h"
#import "PageTitleViewController.h"
@implementation MyTableController
@synthesize myTableView, menuList, controlList, navigationController;
#pragma mark Table View Controller Methods
// Implement viewDidLoad to do additional setup after loading the view.
- (void)viewDidLoad {
[super viewDidLoad];
self.menuList = [NSArray arrayWithObjects:
@"Start",
@"Settings",
@"Instructions",
@"About",
nil];
NSMutableArray *mutableArray = [[NSMutableArray alloc] initWithCapacity:10];
for (int i = 0; i < [menuList count]; i++)
[mutableArray addObject:[NSNull null]];
self.controlList = mutableArray;
[mutableArray release];
- (void)dealloc {
[myTableView release];
[menuList release];
[controlList release];
[super dealloc];
#pragma mark -
#pragma mark Table View Data Source Methods
- (NSInteger)tableView:(UITableView*)tableView numberOfRowsInSection:(NSInteger)section {
return [self.menuList count];
- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {
static NSString *MyIdentifier = @"MyIdentifier";
UITableViewCell *Start = [tableView dequeueReusableCellWithIdentifier:MyIdentifier];
if (Start == nil) {
Start = [[[UITableViewCell alloc] initWithFrame:CGRectZero reuseIdentifier:MyIdentifier] autorelease];
Start.accessoryType = UITableViewCellAccessoryDisclosureIndicator;
UILabel *label = [[UILabel alloc] init];
label.font = [UIFont boldSystemFontOfSize:24.0f];
label.frame = CGRectMake(85.0f, 15.0f, 200.0f, 28.0f);
label.textColor = [UIColor blackColor];
label.backgroundColor = [UIColor colorWithRed:1.0 green:1.0 blue:1.0 alpha:0.6];
label.opaque = NO;
label.tag = kMenuLabelTag;
[Start.contentView addSubview:label];
[label release];
UILabel *menuLabel = (UILabel*)[Start.contentView viewWithTag:kMenuLabelTag];
menuLabel.text = [menuList objectAtIndex:indexPath.row];
return Start;
#pragma mark -
#pragma mark Table View Delgate Methods
- (void)tableView:(UITableView*)tableView didSelectRowAtIndexPath:(NSIndexPath*)indexPath {
NSUInteger row = [indexPath row];
NSLog(@"entering didSelectRow: controlList=%@ row=%d", controlList, row);
if ([controlList count] <= row) {
NSLog(@"return - controlList too short");
return;
UIViewController *targetViewController = [controlList objectAtIndex:indexPath.row];
if ((NSNull *)targetViewController == [NSNull null]) {
NSLog(@"at switch: targetViewController=%@", targetViewController);
switch(row){
case 0: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
case 1: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
case 2: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
case 3: {
targetViewController = [[PageTitleViewController alloc] initWithNibName:@"PageTitleViewController" bundle:nil];
break;
default: {
NSLog(@"return - invalid row no.: %d", row);
return;
if (![targetViewController respondsToSelector:@selector(view)]) {
NSLog(@"return after switch - targetViewController is not a controller");
return;
[controlList replaceObjectAtIndex:row withObject:targetViewController];
[targetViewController release];
NSLog(@"ready to push controller: controlList=%@ targetViewController=%@", controlList, targetViewController);
[[self navigationController] pushViewController:targetViewController animated:YES];
@end

IPhone Development - Switching Views

First, let me mention that this post may be in the wrong forum, so if that is the case, please let me know to repost.
Next, my question is very simple. I have two views. The first has a button. The second has some text. I want to switch from the first, which loads when the app starts, to the second. This should be pathetically easy, but I have yet to figure out how it's done. At this point, their must be a fundamental problem with the way that I am thinking about how Windows and Views are managed, because based on my current beliefs, I cannot figure the rest out. I have created several "1-View" applications and, for what I am trying to do, have created several Views each of which do what I want them to do. But, I cannot find a way to switch from one to the other. I go to several homemade videos of people doing it, but no two people do it the same way and they all have their own little tricks to getting it done. This leads me to believe that it's not simply a matter of a lack of documentation by Apple, but that Apple doesn't even have a standard. Instead the have several hacked-together solutions that each can kind-of work depending on the situation.
Here is the way I am conceptualizing it and maybe someone can show me the error in my thinking. I create a View-based application for the iPhone. I believe that the AppDelegate class that is created for me appears to really just be a Window/View manager class in that it keeps track of the one and only Window and manages which View is currently being displayed in that Window. Then, there is the MainWindow.xib file which is really confusing, because it simply populates itself with whatever is in the ViewController.xib file. It's never even mentioned in any of the code I am given. I imagine it is mentioned elsewhere, but that is irrelevant.
Now, the ViewController.xib file is used along with Interface Builder to create a View from Widgets and link those Widgets' references and corresponding actions to class variables and methods in its corresponding ViewController.h and ViewController.m files. So, it would follow then, that if I wanted to create a second View, so that when a button on the first view was clicked a new, second View would be shown, I would create a new "View.xib" file and corresponding .h and .m files for it. Then, I have a method in my AppDelegate that takes a UIView object and removes whatever view is currently the subview of the window and adds the parameterized view as the new subview. This is also where I would put my transitions.
Now, the new View that I just created doesn't contain the Title Bar or whatever it's called where the battery monitor icon, carrier icon, etc. exist, so this means that whenever I am actually putting Widgets in the View I have to just remember to avoid it and that the "auto-alignment" thing is off. So, I try other options, and create a new "Window XIB". This blows my freakin' mind, because it appears to be what I want despite it being called a Window and not a View. So, I try the "Write Class File", and it creates a new class called UIWindow which is a subclass of UIView. But wait, aren't Views supposed to be what populates the Windows, and UIWindow is a class that already exists. AHHH!!!!
So, I rename the class to SecondView and create an instance of it in the AppDelegate. Now, I go into the AppDelegate.m file and change "window addSubview:viewController.view" to "window addSubview:secondView.view" (Edit: Brackets aren't allowed, so I am using quotes in their place here.) which doesn't compile, because it is a subtype of UIView which doesn't have a view member variable, only UIViewController does. So, I change it to make it a subclass of UIViewController which has a view member variable, and it compiles and shows a blank white screen of which neither of my views look like. Then, I go shoot myself in the face. It would appear that I need to link the new SecondView class to the SecondView.xib file somehow.
It appears that the AppDelegate class should manage nothing and should only have a single UIWindow object that it loads. Then, the View Controller which has a View object should really have an array of all Views and should populate its view object with the currently needed View. This would make sense except that of all the How-tos I have seen none of them do it this way. I am sure that I didn't say everything that I need to say, but at this point I am so infuriated that I cannot think straight.
<rant>
I have developed in several different environments, and I have never come across such a simple and common concept implemented in such a convoluted way. Maybe I am simply missing something obvious, here, but if that's the case, Apple please please please make the documentation far less cryptic. I feel like I'm walking blindly through a jungle when I try to read the How-to documentation on your site. If I need to know some information about some class then it is relatively easy to get to, but trying to figure out how to actually do something within iPhone development is painful.
I began trying to develop for the iPhone by just diving in and seeing what happened. That sort of failed, so I began reading your online help documentation and believe I took a step backwards. Finally, I bought a book on Objective-C that concluded with creating an iPhone app. I read it in a few days and now feel that I am rather proficient with the language as well as creating applications on the iPhone as long as they only consist of a single View in the ViewController class. All I want to do is switch from one View to another, and it shouldn't be this hard.
</rant>
Message was edited by: PhoenixRebourne

Well odds are you won't find what you are looking for here unless another developer happens to come here. These forums all withing the support area are user to user forums to help with issues of usage, repairs, etc.
Doesn't the developer area where you signed up to be a developer have forums?

What am I doing wrong? Switch Views??

I am writing an application for the iphone. To start, I created a View-Based Application in XCode. On the main view there is a UIButton. Then I created a second view called View2.xib which has a UILabel that says "Second View". Very basic.
Now, all I want to do is display the second view when you click on the button. In the view controller class for the first view that contains the button I added.
#import View2ViewController.h
View2ViewController *View2;
I also added the property for this, etc. This class also has the IBAction for the button click event, which works just fine and executes when clicked. Now, in the .m file I obviously @synthesize View2; and begin to edit the button click method to display the view. Here is the code:
Code:
if(self.View2 == nil) {
View2ViewController *two = [[View2ViewController alloc] initWithNibName:@"View2" bundle:[NSBundle mainBundle]];
self.View2 = two;
[two release];
self.navigationController pushViewController:self.View2 animated:YES;
Everything complies, and runs. When I click on the button the application does NOT display the second view. Nothing crashes, but it doesn't display the view. What am I doing wrong? I have everything linked up in Interface Builder.

I figured this out. You have to remove the current view from the window and then add the new view via addSubView: after it is loaded from the nib file.

Problem with switching views

I have a web browser that has a view that has links to popular sites on the web. I have 2 problems:
1. The webview reloads when I swich the view.
I am using to method to switch views:
{code}
-(IBAction)swicthview:(id)sender {
    QuickSites *quicks = [[QuickSites alloc] initWithNibName:nil bundle:nil];
    [self presentModalViewController:quicks animated:YES];
{code}
And this to swtich back:
{code}
-(IBAction)switchback:(id)sender {
    Brandsonic_Web_mobileViewController *quicks = [[Brandsonic_Web_mobileViewController alloc] initWithNibName:nil bundle:nil];
    [self presentModalViewController:quicks animated:YES];
{code}
2. I cannot acess the webview object in my view controller.h
What can I do about this problem?

If you wish to switch back to your parent view
In your switchback action write the following code
[self.parentViewController dismissModalViewControllerAnimated: YES];
OR
[self dismissModalViewControllerAnimated: YES];

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

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.

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

Switching view controller crashes

Similar Messages

Maybe you are looking for