I have UIImageViews in three different view controllers displaying the same thing, that being user's profile pic. I want them all to update at the same time when the user changes his/her profile pic using imagepickercontroller. I thought about outlet collection, but I believe they don't work across different view controllers. I am out of ideas on this one, any help would be greatly appreciated. Thanks.
I think there are few solutions for your problem. One of them is using your profile image as global variable. Then whenever you move to a viewcontroller, in their viewWillAppear, assign the profile image to the UIImageViews.
It's simple, isn't it?
Related
I'm making an iOS app that shows profile images of friended users on a single page. There might be more than one identical profile image for each user displayed on the same page at any one time. The images are subviews of various custom views. Long pressing on one of the images allows the user to change it. After they have done so, all identical profile images on that page (x number of images) should be changed to the new image.
How can I get all UIImageViews on the page that contain the same profile image to update, without having to set each one individually?
Ideally, I would like to 'reload' the view controller, but I can't find a way to do this. I have tried using setNeedsDisplay(), but it doesn't work.
I'm new to iOS development.
OK, I solved this by subclassing UIImageView and adding a 'user' instance property and an array of all initialized instances as a static property. Now when a profile image is changed in one imageView, I can iterate over all instances and swap out any that belong to the same user.
I created a custom SplitView class that subclasses from NSSplitView. Everything looks right to me, and works fine, except the divider. For some reason it doesn't want to show up between my views of a SplitView.
Any kind of hint or help is highly appreciated!
here is my setup in the nib:
and here how it looks when I run it
interesting thing is, that when I move the mouse to the place where the divider should be, the cursor changes and I'm able to drag it...but for some reason it doesn't look right
You can change the color of the divider using the 'drawDividerInRect:' function to change the color of the divider by passing your own rectangle. It is also possible you moved one of the custom views in the split view and can't see the divider anymore. You could try selecting the different views using the object hierarchy.
I've found that apple doesn't like to make it easy to modify a lot of their different views and controllers, probably because they are trying to maintain some uniformity in the apps that are run on their system.
Is the hidden check box checked?
I have seven views that I need to navigate between from any of the other views. I don't want to keep doing segues from each one as new instances would keep being created...among other issues. What I was originally trying to do was have all the segues start from a home view and then go to the designated target view. When the user left that target view a public variable would be set if they wanted to go to any other view other than the home view. When the home view reappeared, it would check that public variable to see if another jump was needed. In the Home view I put the segue jump check in the -(void)viewDidAppear:(BOOL)animated function. The problem with this being you see the home screen for a second before it goes off to the new target view. The -(void)viewWillAppear:(BOOL)animated does not work for segues. I guess this is because it hasn't fully released the old segue yet?
Is there a better way to handle a freeform many view navigation issue like this? If anyone needs it, I can post some sample code for what I was trying to do. Thanks in advance for any help.
It sounds like you need a UITabBarController.
It allows you to have multiple view controllers, and switch between them by tapping the tab on the bottom of the screen.
It allows you to have only one instance of each controller, so that as you switch between them, data persists and you aren't creating new instances each time.
Here is an example of what one looks like (notice the tabs at the bottom of the screen):
(source: xamarin.com)
First off this is Xcode 4 iOS 5.0. Here is what I want to do. I have one view, we will call it view1, which has a button and when that button is pressed a different view with a table appears called tableView. I have multiple images I want to be in this table and when the image is selected, it would appear in view1. I have already researched all of this and just can not find the right material. The button and table are already working together and I can add the objects to the table, but getting those objects that I select to appear on view1 is what I am not understanding. I can not get the two nib files to work together, or Im going at it wrong.
Second question, guess this is similar, view1 displays an image that is selected from the photo library BUT is there a way to open the photo library, select the photo, and have it appear in a DIFFERENT nib view? Again this is getting the NIBs to work together. I would appreciate all the help I can get. (photo library and selection of photo already works so that code is not needed). Thank you for the help!
I have used this example to get what you have described in the above question. But with some tweak in the delegate methods and hop you will get some direction for your problems, too.
Good Luck!
Happy Codding! :)
And need any help just ask for it, don't hesitate.
It is possible from delegates in other class.
I’ve been reading through several books on Mac development, but cannot find the information I’m looking for.
The books all describe how to make floating windows or panes, but never mention how to make them all in one window. A simplified example of what I’m looking to create is shown below:
Basically, there will be three windows; A selector window with radio buttons to choose which NSDocument is currently being used, a window underneath that with buttons that show different windows to the right that allow viewing and manipulation of certain data.
For a example, each NSDocument may have a color value that can be set in the window shown by clicking view A, and some text strings that can be set in the window shown by clicking view B.
So the questions are:
Is it appropriate to use a single NSDocument sub-class for each Doc #1 and Doc #2?
Which classes should I use to set up the application as shown? NSWindowController? NSWindow? NSPanel?
I’m only looking for guidance on what to read up on, so any pointers are appreciated.
EDIT:
To clarify this further, I want to have a table view where the buttons are (View A & B), and by clicking them they will cause the other window/view to change it's contents.
It's like the split view in the iPad settings application, there is a table view on the left, and when it's pressed the right side changes.
The radio buttons are there only to illustrate that I want more than one Document. I'm guessing I need more than one to handle this? Or perhaps I should place them all in a single NSDocument? Somehow that doesn't seem right.
To achieve what you want you need one window (NSWindow), one window controller and various views each with their own view controller. There are several ways you could set this up, all depending on your requirements:
You'd have at least 3 views (instances of NSView): one for the selection of the document class, one for the view selection and one for the content. Each view is controlled by a view controller (instance of NSViewController). Additionally you can opt to wrap the views in split views (NSSplitView) so your user can resize the real estate available to each view.
You have one window with a window controller. If you choose a Document based app template in Xcode, Xcode will generate a subclass of NSDocument which you can use as your window controller (or choose to use Core Data and Xcode will generate a subclass of NSPersistentDocument with all bells and whistles you need to access Core Data for document persistency).
So to come back to your questions:
1: Yes, but depending on your requirements. If Doc #1 is a completely different thing than Doc #2 than you might need to re-evaluate. For example Doc #1 might have completely different persistent requirements than #2.
2: There's no single scenario here, but one that worked for me: Take the project template for a document based app (with or without Core Data). Use the generated subclass of NSDocument (or NSPersistentDocument) as your window controller. Use NSView to implement the views in your window where each view is managed by its own controller, which is an instance of NSViewController.
I know this is an old question, but a way to do it how you want would be to use: ContainerViews and set their embed segue to be the view controllers you want.