Hi Mark,
ng-checked and ng-selected do serve another purpose then ng-model. Mostly
one will use those while building custom checkboxes or selection widgets.
The main difference is that those don't have 2 way binding.
Mostly those are used for hinting default's and stuff like that.
Regards
Sande
That seems like an uncommon thing to want to do. So my conclusion is that
in most cases it is better to use ng-model than ng-checked or ng-selected.
On Tue, Jan 14, 2014 at 5:10 AM, Pan Stav wrote:
> See that example of ngChecked?
> http://code.angularjs.org/1.2.4/docs/api/ng.directive:ngChecke
See that example of
ngChecked? http://code.angularjs.org/1.2.4/docs/api/ng.directive:ngChecked
If it was ngModel used instead, checking / unchecking the "slave" checkbox
would also affect the master checkbox.
On Tuesday, January 14, 2014 4:15:55 AM UTC+2, Mark Volkmann wrote:
>
> Why would one c
