Skip to content

readOnly rows implemented. - #4

Open
0xMarK wants to merge 2 commits into
alexleutgoeb:masterfrom
0xMarK:master
Open

readOnly rows implemented.#4
0xMarK wants to merge 2 commits into
alexleutgoeb:masterfrom
0xMarK:master

Conversation

@0xMarK

@0xMarK 0xMarK commented Nov 19, 2012

Copy link
Copy Markdown

Now there can be some values that cannot be checked/unchecked. Their
initial selection state will remain read-only.

Now there can be some values that cannot be checked/unchecked. Their
initial selection state will remain read-only.
@alexleutgoeb

Copy link
Copy Markdown
Owner

Thanks for your pull request. I'm not sure if this is a feature that will be used quite often, so we should make this delegate method at least (at)optional.

Can you point out some use case where this might be useful?

Cheers,
Alex

@0xMarK

0xMarK commented Nov 20, 2012

Copy link
Copy Markdown
Author

I'm developing an enterprise application with a complicated user access rights. In few places the app must forbid the user from unchecking some rows while letting editing all other rows. (The user can only see that the row is checked)

I've integrated this modified version to my project and it works great!

Of course this feature isn't needed often. So you are absolutely right, I will make the delegate method optional.

ALPickerViewDelegate method pickerView:readOnlyStateForRow: made
optional.
@alexleutgoeb

Copy link
Copy Markdown
Owner

Thank you, that looks good, will test this in one of my own apps and merge your pr in master shortly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants