Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8775539
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T18:49:29+00:00 2026-06-13T18:49:29+00:00

I am posting this question to get suggestion about an issue. FYI… I have

  • 0

I am posting this question to get suggestion about an issue. FYI… I have tried approaches 1 and 2, but I am not satisfied with the outcome from programming (and partly UX also) perspective(s).

I have a table which has 2 sections. Each section has 4 cells. Each cell contains a textField. When the user presses Edit button (located on the navigationBar), the user can change the position of the cells, i.e. – s/he can move the cells from one section to another. Simple!

So far I have been considering three approaches.

  1. Include a UIButton object with each cell. The button could have an image of + or -. – move cell from second section to first and + moves cells from first section to second. But once the change has been made, the image of the button should change from + to – or vice versa. But I realized that I cannot change the image of the button programmatically. So I will have to make two sets of buttons for each cell => 16 buttons + 16 button @property to change hidden from YES to NO and opposite. I personally think this is not the best approach. Even worse, I will have to keep a track of the index where the cell should appear when it translates from one section to another.

  2. Have 8 cells in section 1 and 2. 4 cells of second section appear as hidden in the first section and vice versa. When the user presses + in one section A, its property should be set to hidden in section A and it should be made visible in section B. However, when the cell’s property is set to hidden, a void is created in its place which looks very ugly. Is there a way to fill the void? Also, if I use a grouped cells, the remaining cell at the end of section will not have rounded bottom corners.

  3. User can drag cells from one section to another. (FYI.. drag is represented by three horizontal lines.) Issues: how popular is the drag feature? Will the users interpret it without being suggested by the app? If this the best approach, how do I implement it?

I would be glad if you kindly help me pick the best option.

Thanks!

Cheers!

Edit 1:

what if there were three sections, is it possible to change/ move fields between 2 and 3, without making any changes to section 1?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T18:49:30+00:00Added an answer on June 13, 2026 at 6:49 pm

    Option 3 is the standard approach and already implemented by UITableView and its data source and delegate methods. Users are used to using this standard interface.

    All you need to do is implement the appropriate data source and delegate methods involved with moving rows – three in total.

    If you have any questions about implementing the three methods, see the Table View Programming Guide for iOS for details.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Before you all get pissy about me posting this question again, let me explain
Sorry to be posting this question. :( But I have spent almost the entire
ok ... sort of have been dithering on posting this question but here goes:
I'm posting this question not because I am getting some errors but because I
I searched StackOverflow before posting this question but I wasn't able to find the
It might be a long shot posting this question here but we will see.
Edit: I've learned much since the posting of this question, and so I have
This question is already answered. I discovered what the problem is. But, I'm posting
this is my first time posting here, I have a question which I have
I have considered posting this question on GameDev since my case relates to a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.