Readonly mode as opposed to disabled about eureka HOT 9 CLOSED

@tp
it's not a common scenario. Let's see if someone else ask for it to define if it worth adding it.
Anyway I think you can easily accomplish it by doing:

        for row in form.rows {
            row.baseCell.userInteractionEnabled = false
        }

from eureka.

I too would say this is a 'nice to have' feature. I know it's not too dofficult to do the workaround but still it would look clean if I didn't have to call the baseCell.

from eureka.

I also think this is a nice to have future. I think this workaround:

       for row in form.rows {
            row.baseCell.userInteractionEnabled = false
        }

is not so good because it disables all kinds of interactions with the row, including scrolling, which is a interaction that a readonly mode should be able to handle.

My workaround for this was:

class ExampleViewController: FormViewController, UITextViewDelegate {

    override func viewDidLoad() {
        super.viewDidLoad()

        TextAreaRow.defaultCellSetup = { cell, row in
            cell.textView.delegate = self
        }
    }

    func textViewShouldBeginEditing(_ textView: UITextView) -> Bool {
        return false
    }

}

from eureka.

Not really because if you make row with user interaction == false, then events are not fired, and therefore it cant react to selections...so its not a solution

from eureka.

Thanks this solves the issue nicely and looks exactly as I would expect from a "read-only" mode. :-)

from eureka.

So can you extend read-only to fields as well ?

from eureka.

Not really because if you make row with user interaction == false, then events are not fired, and therefore it cant react to selections...so its not a solution

Hi, did u solve this problem?

from eureka.

I've done some PR, wasnt accepted #1653

from eureka.

I did in this way

form +++ Section("DATA")
             <<< TextRow() {
                  $0.title = "Code"
                  $0.tag = "Code"
                  $0.cellSetup { cell, row in
                  cell.textField.isUserInteractionEnabled = false
               }
               }.onCellSelection { cell, row in
                   let codeSectionViewController = CodesTableViewController()
                   self.navigationController?.pushViewController(codeSectionViewController, animated: true)
}

for my case I need to move to another view controller, to select multiple values and to return the selected rows back, for start I used MultipleSelectorRow, but I had troubles to display my object in MultipleSelectorViewController. For that I disabled the textfield, and each tap is detected by baseCell and it pushes to CodesTableViewController.
Back I sent data through delegate.

I decided to use this way instead to create my CustomMultipleSelectorRow.

from eureka.