I'm pretty new to objective-c and I am working on my first app, I changed the design a little bit on it to make it look more nice and it was working fine, but then it started crashing every time i pushed a button. And now when i run it it looks like the way i had designed it before. but it still looks normal in my storyboard. This has happened to me before so i just made a new project and copy and pasted the old files and storyboard into the new one and it worked fine until now. Can anyone help me?
Related
In every project I do, I tend to have the same problem with my Xcode
I am new to swift programming learning it for about a week, but because of this problem, I can't go on with my lessons. I create a new project.
So I begin like this And basically I don't know another way to do it. Then I configure it like this which is I guess the only option. Then I add a label from the library, open the assistant, and control drag to connect it after the connection is made I cannot get to the properties of the UI element. In the identity inspector ViewController class is connected as well As it is shown here. Would you tell me what am I doing wrong? Because I am stuck. I am new to this and I know the problem must be small but I can't proceed.
I'm in the process of comparing MvvmCross with ReactiveUI for a major pharma project on Win Store, WP8, iOS, Droid. We've already selected Xamarin.
I'm totally new to ReactiveUI. I really like what I see in principle, and I think Paul is a genius. However the details are becoming a real bear. I've spend several days tracking down documentation (the manual is from 2011 and seems almost entirely outdated - it doesn't even contain the word "Router") and sample code.
I'm looking at the sample from ReactiveUI.Samples
Also the project MobileSample-RT from the ReactiveUI solution.
I based my little hello world on the ReactiveUI.Samples "Routing" example. Frankly this isn't much of an example as all it does is navigate from AppBootstrapper to the one and only view. I'm trying to do something similar to the "three page" example from MobileSample-RT. The problem is, if I try something like this in my project:
HostScreen.Router.Navigate.Execute(RxApp.DependencyResolver.GetService(typeof(LoginViewModel)));
It crashes (pdb symbols not loaded in ReactiveUI.dll)
If I try this:
HostScreen.Router.NavigateCommandFor<LoginViewModel>().Execute(HostScreen);
Same result - hard crash. That really threw me as it seems like something that should "just work".
I can call this:
HostScreen.Router.Navigate.Execute(new LoginViewModel(HostScreen));
And it does go to my view, as expected. I also wired up a back button in the main screen:
this.OneWayBind(AppBootstrapper, x => x.Router.NavigateBack, x => x.BackButton.Command);
And that indeed moves back from the view to which I'd just navigated.
So now I want to move forward again. I click on the button that does this (again):
HostScreen.Router.Navigate.Execute(new LoginViewModel(HostScreen));
And I go back to that view. However this time it takes 2 clicks on the back button to get actually move back. If I then move forward again, it takes 3 clicks the next time. The NavigationStack is filling up with new instances of LoginViewModel.
So, what IS the correct way to do routing/navigation? Why are those commands crashing? Rather than calling "new" each time in the Navigate.Execute, how do I navigate to a viewmodel that is already in the navigation stack (or should it be there in the first place?).
Many thanks for any clarity you can provide.
If you're building for iOS and Android, you simply don't want to use Routing - the notion of routing conflicts too much with what the platforms want you to do (even on WP8 it's a stretch but I was able to hacky make it work). You should stick with View-first location.
However, if you're using Xamarin Forms, ReactiveUI works great with VM-based routing (since Xamarin managed to do all the hacks to make it possible!). Check out https://github.com/paulcbetts/xamarinevolve2014 for a demo of it
I know the docs suck and I'm working on new ones:
https://github.com/reactiveui/ReactiveUI/pull/391 - Pull Request / Progress
https://github.com/reactiveui/ReactiveUI/tree/docs/docs/basics - Browsable version
Background: I have been wanting a PickerView that is exactly matches that of Safari. I looked through many Gits and found none that work quite as exactly. I decided to build my own. It is complete now, but there is a bug that would not go away.
Problem: If you run the sample project you will be greeted with 2 text fields.
Tap on one of the textfields - it brings up the BTPickerView. Everything works just as you would expect.
Choose the fourth choice, then press done.
Tap on the same textfield. This time, the debug log will show you that you have executed an infinite loop, which freezes the app.
Question: What did I do to cause it? And how do I fix it?
I have tried everything to boil it down. It comes down to this and I could not go any further. Please advise.
Edit: Here is the sample code you can download in case anyone missed the blue link above.
The issue seems to be with the constraints in BTPickerLabel. If you temporarily disable the constraints from BTPickerLabel, code works fine. Enforcing constraint might trigger the reloading of entire picker view infinitely. I hope it should help you to fix the problem.
I've been working away at a project of mine, when a couple days ago I noticed that changes I was making to the MainStoryboard.storyboard weren't occurring in the published version of my app. I tried adding new components and switching many elements and still no changes. I've tried cleaning and building, but the storyboard will still not update itself to my new changes. Changes I make to the code, however, work. I can dynamically populate a text field for example.
I feel like I've done something silly and not realized it, like somehow disconnected or duplicated the storyboard (though I only see one storyboard file in my list). I'm hoping someone has some ideas so I can progress with my project. Anyone?
I had the exact same problem and it was due to localization which splits the storyboard into different ones for each language. It remains one file but xcode shows each localization in the address bar (or whatever it is called) if you select the storyboard in the file navigator.
Most likely you made changes for a storyboard language you don't use yourself for testing.
i've inserted a view before an established table view if that makes sense. ie. i had an app with a first and second view, then i put another view before the first view, now the content doesnt show up in the (now) third view!? Any ideas why that would be? Would i make to make some changes in the app delegate maybe??
Thanks
EDIT:
Sorry, i wasnt sure which bit of the code would be relevant to my problem and i didnt want to flood the post with my entire code so i zipped it up if anyone can help?
Thanks
Source Code
Here is complete tutorial for a table view with navigation.
your question is extremely vague and confusing, hopefully next time you can provide some code and you might be able to get better responses from the community