objective c - Buggy navigation controllers, porting iPhone app to the iPad -


I have a fairly simple iPhone application, which I want to run on both the iPhone and the iPad. I just want to be a bigger version of the iPhone version in the iPad version, I've been enhanced or not - I'm working on an iPad-specific version of the app that makes better use of the interface, but I wanted to make sure that my current There is something among the customers.

The app is a simple tab-based application, and within each tab is a navigation controller that presents a table view, each of which has some layers below. Everything works mostly - I have some examples of scenes of filling space available, but I can fix it. My biggest problem is that navigation controllers break universally when I try to use them.

Let me try to explain in more detail:

A tab begins with a "year" table view, which are entries all year; If you tap in a year, then another month with another month is pushing the table in which the entries are; If you tap in a month, it will put another table view that shows the individual entries; If you tap an entry, it gives a view (a UIWebView , with some extra widgets) that shows the details of an entry.

Each push is done with [navigation controller Push ViewController: foo animated: yes] . The three table view controllers mentioned above have been created from all the same nibs (in fact, pushed to any navigation controller in any tab, everything loads with the same nibs). Since I know that there are only three levels of navigation, I have allotted three similar visual controllers and use one, two or three depending on how many entries are there.

These controllers seem to mess up the "back" button universally the view controller status, so if I drill on the third scene - showing everything in a month - I first Not able to pop up all the way till the scene: If I pop a level then the back button stops working

Another example in another tab: It is a table view that You can tap on any entry , And a new view controller will be pushed which shows the details of that entry. If I tap on an entry, tap the back button, tap the login again, there is no back button visible, or sometimes, text Which appears inside the back button, appears, but no button appears!

This behavior occurs when I run the iPhone app in Scalched mode (built with original SDK 4.0, supporting OS 3.2) or in native mode (built with Base SDK 3.2) I am trying. It runs without problems on the iPhone, I'm at a loss here, because this stuff always used to "just work" out of the box, most basically the first time I made it when the back was installed.

Tell me the nature of my programmer that I am doing something wrong in my approach navigation, and that the iPad is just exposing it, but I can not understand how it is.

Has anyone participated in an issue like this or could suggest what is going on or there might be a better way to debug it? The issue was that I had a range on NSMutableArray, which had methods like Stack push < / Code> and pop . This problem was fixed by removing this class category.

WTF, though.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -