Simple OK-message view (like Confirmation, but not a question)

Am I missing something or is there no inbuilt view for a simple message with an OK response for use in an app?

I'm aware of the Confirmation / ConfirmationDelegate, but I want to just display a message that the user can confirm (rather than the yes/no response that Confirmation gives) and there doesn't appear to be a way of doing it.

Please make me look like an idiot and point me at the very obvious solution.

Cheers,

Tom

0 Tom101449 over 4 years ago

I'll assume from the lack of responses, I'm not being an idiot, and this seemingly obvious functionality doesn't exist

0 jim_m_58 over 4 years ago in reply to Tom101449

couple of ways to do this. Just use a 1 item menu with "ok" or just display "Ok" and have an input delegate that looks for input when the "ok" is displayed. For example, if I display a summary at the end of an activity with "Back to exit", I know I'm in that state, and react accordingly in onBack()

0 Tom101449 over 4 years ago in reply to jim_m_58

Thanks Jim.

So in effect it's simply a view with a message in the middle and an delegate to pick up on a click over the entire view?

0 jim_m_58 over 4 years ago in reply to Tom101449

You don't even need a separate view. Just the logic in onUpdate to display "ok" and the delegate for that view need to know you are waiting for something when OK is displayed. Views can be very expensive memory wise, and I use them sparingly.

In one of my apps I have about a dozen screens, and one view, other than if I push a menu or a MapTrackView.

0 Tom101449 over 4 years ago in reply to jim_m_58

So unless I'm missing something (and it's highly possible as I'm a ASP.Net developer by trade) it's a compromise between complex logic to show/hide things vs memory of a simple view.

OK, will have a think/play

0 jim_m_58 over 4 years ago in reply to Tom101449

I first used C in the mid 70's, used Assembly, c++, Smalltalk, Java. python and others along the way. There is a trade off between performance (memory and speed) based on how an app is written.

For basic input stuff, have you looked at the input sample in the SDK? The record sample also shows the basics of a recording app.