This seems like it should be straight forward, but I'm having trouble solving it.
I will simplify the problem to get to the heart of the question.
I am building a Xamarin Watch OS 3 app. I have an InterfaceController1 and an InterfaceController2 on my storyboard. I added a button to InterfaceController1 and created a segue to InterfaceController2. I made it a modal.
On InterfaceController2, I have Picker list. I want to choose an item, close the modal InterfaceController2 (which automatically sends me back to InterfaceController1), and have that data (whatever I picked from the list) available in InterfaceController1.
This seems very basic...why else would you pop up a modal if not to make a selection and return back to the main scene. But I can't seem to figure it out. I see examples for iPhone apps, but they don't seem to apply for Apple Watch apps. Unless I am misunderstanding something.
Related
I'm trying to implement a sidebar like the one used in the macOS Notes app. I've got the storyboard and sidebar working. But how can I implement the content window / detail view on the right? I want to show something based on the selection made in the sidebar. I tried doing it by hiding stuff in one view but it gets messy real quick. I'd rather switch views in the same window somehow. What is the commonly accepted way of doing this?
Is there any way (that would be accepted by an AppStore review) how to open the today view of the Notification Center? I searched the docs for NSNotificationCenter but if there is a way, this seems to be the wrong place to look.
My requirement is, that I am developing a Today Extension for the Notification Center. The main application is only used to configure the settings of that extension. All content is displayed in the widget. Now I want to implement notifications: If there is new content in the widget I want to send a push notification. When the user clicks the notification in the top right corner I would like to open the Notification Center and focus my widget (if the user has many widgets, it might not be in the viewport).
I have a strong guess this is not feasible. I hope someone can prove me wrong.
You have reached a dead-end.
There is no api or event to support display of TODAY notification view.
It is left for users 'will', when he wish to navigate to TODAY view, as otherwise it can easily become a inconvenience.
I have tried to get the data-role="backbutton" kendo mobile ui feature to work but I am having issues. When testing the app on my iPhone 4 I get stuck in my app because the back button breaks the UX.
What happens is that when I am testing, I click heaps of back buttons (as they are used quite heavily in my app) and then randomly one decides to slide the previous view into the screen but only goes halfway and then snaps back (or some other type of visual glitch occurs). Then after that, all my navigation breaks down and I get stuck in the last view that I was in. Or better yet the links go to places that they are not supposed to. My tab bar does not work and either do links in the header. I have to exit the app completely, remove it from operating and try again. Seriously something wrong going on here.
I have tried to programatically add the back button by following the Kendo UI documentation but that does not work either. I am left with a button that does absolutely nothing when clicked - it may not even solve the issue anyway. I have looked using developer console in Google Chrome but I can't see any obvious issues.
Has anyone using Kendo Mobile UI experienced this issue before?
I downloaded the latest release of the Kendo UI build and the problem seems to have been resolved. Surprising! I assumed the Kendo framework was a bit more mature to be experiencing such a big issue. It was occurring when using slide transitions in navigation. Here is a link to the bug post on Github https://github.com/telerik/kendo-ui-core/issues/66
I've been messing around with the new iOS7 SDK and I want to make a back button like there is in most of the other OS apps. Heres a screen shot of what I'm trying to do:
But I can't figure out how. I've never really messed with interface builder because I usually code with opengl apps, so any solutions would be much appreciated. Thanks.
That is is standard "back" button. You get this when you use a navigation controller and show one view controller then push a second. The "<" means "go back". The "September" part is the title of the previous view controller. You don't need to create one of these. Just make proper use of a navigation controller and a couple of view controllers and it will appear automatically.
I've implemented a Share Picker Extender (which lets you share a photo from the Pictures hub to your app via a special token), and would like to close the app once the user has clicked on the button to upload the photo, as the built-in Facebook app does.
I'm aware of the many questions re terminating apps - I'm just wondering if I'm missing something for Share Picker Extenders ... Telling the user "Now press the back button" seems pretty ugly, but perhaps it is the only (certification worthy) way. If you've implemented a Share Picker extender, what have you done?
I wasn't able to figure out a good way to handle this either. I detect that users have gone back to my first page and say "Click here to go to our main app" and "Click back to go pack to Pictures". And if they click the first one, Navigate("MainPage.xaml");. You have to make sure you don't accidentally prevent them from leaving. I asked this question awhile ago in this thread and got no response.