3 Answers

• I have posted a complete solution using NavigationGroups here

  http://blog.clearlyinnovative.com/post/1624173028/titanium-appcelerator-quickie-navigation-groups

• Aaron,

  Thanks much for the sample code. While I had tried passing an object reference to the navgroup as a window property, I had not also tried passing the parent and root windows as objects.

  As you note, popping back to the root controller is not pretty. In order to make it more dynamic regardless of the sequence of windows used to navigate to a given window, I made the following tweaks:

  In app.js around line 29 when assigning properties to the first window beyond the root, I added another property:

  level: 1,
  

  Then each time I need to open another window, for example near line 10 in your detail_window1.js, I use this:

  level: Ti.UI.currentWindow.level + 1,
  

  By tracking the nesting level, I can at any time pop back to the root using this code:

  btnHome.addEventListener('click', function(data)
  {
      nextWindow = Ti.UI.currentWindow.parent;
      for ( i = 1; i < Ti.UI.currentWindow.level; i++ ) {
          closeWindow = nextWindow;
          nextWindow  = nextWindow.parent;
          Ti.UI.currentWindow.navGroup.close(closeWindow);
      }
      Ti.UI.currentWindow.navGroup.close(currWindow);
  });
  

  That makes a standard way to drop a button on any form and be able to "go home" without worrying about the nesting involved. It essentially closes each parent window except the first, then finally closes the visible window returning you to the root controller.

  Thanks for the ideas!

• Aaron,

  I have another question. When I run your project in the OS 4.1 simulator, when I advance to test window two, the console show this error in red:

  [ERROR] Value was not the value expected. (containsChild) was not (YES) in- [TIViewProxy childWillResize) (TIViewProxy.m:1194)

  I get this whether I use Titanium SDK 4.1.1, 4.2, 4.3, or 1.5.0 – do you know what causes this? Your project continues, but I am seeing the same error in another project of mine which aborts, and I could not find the cause. But now I am not sure it is directly related to what makes my project fail.

  Do you know what causes this error in your project? Is this just an assertion they are testing in the TIViewProxy module? Is it safe to ignore it?

  Thanks again.