Home/ Questions/Q 6380457
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:16:12+00:00

This is more a question of what is generally good practice in iPhone coding.

  • 0

This is more a question of what is generally good practice in iPhone coding.

I have a scroll view with UISegmentedControls, submit buttons, UIActionSheets, zooming, and close buttons that show temporarily.

Should I just be piling all of the method calls (target-action for UIControls) (which are not really formal delegate methods) and zooming delegate methods for UIScrollViews into this one view controller? Or would it better practice to create a new [delegate] object to handle the functionality of these.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think, best place for all this is a view controller.

    My idea is that according to MVC model, managing UIControl’s action or some zooming is neither a work with data (M) or some displaying (V), so there is only one place for this – controller (C).

    Of course if some UIControl event causes data-management, you should (ideologically) do it in model, but model methods should be called from controller anyhow. I think it’s not the best way to make direct connection view<->model.

    • 0