First toggle do not change ngModel value about angular-bootstrap-switch HOT 14 CLOSED

Could you please add a demo?

from angular-bootstrap-switch.

Yes of cause, forgot to link it :) http://plnkr.co/edit/MxCNknpYx4SMaWqrOyRY?p=preview

from angular-bootstrap-switch.

Sorry hit the close button

from angular-bootstrap-switch.

Yeah i have exactly same problem! NgModel isn't updated for the first time.

from angular-bootstrap-switch.

This is probably due to some late binding stuff I am trying to get rid of in the next release.
Thank you for reporting this!

from angular-bootstrap-switch.

I actually think this is happening because you are not returning the value from the $formatter.

   controller.$formatters.push(function (newValue) {
        if (newValue !== undefined) {
          $timeout(function () {
            val = (newValue === getTrueValue())
            element.bootstrapSwitch('state', val, true);
            return val;
          });
        }
      });

Have not tested the code above, but that should fix it...

from angular-bootstrap-switch.

I was having a similar problem but figured it out. I was looking at the demo above and it seems it isn't using the version that has the bottom wrapped in a timeout. Hope that is the problem.

 $timeout(function () {
var isInitiallyActive = controller.$modelValue === getTrueValue();
// Bootstrap the switch plugin
element.bootstrapSwitch({
state: isInitiallyActive
});
// Listen and respond to model changes
listenToModel();
// Listen and respond to view changes
listenToView();
// Set the initial view value (may differ from the model value)
controller.$setViewValue(isInitiallyActive);
// On destroy, collect ya garbage
scope.$on('$destroy', function () {
element.bootstrapSwitch('destroy');
});
});

from angular-bootstrap-switch.

@kfiil, could you please try again with the latest version in the develop branch?
Thanks.

from angular-bootstrap-switch.

Just tried myself, it works on the develop version.

http://plnkr.co/edit/afqDkKJO2MAsYyl7zAHE?p=preview

from angular-bootstrap-switch.

I have just updated everything and still same issue.

from angular-bootstrap-switch.

@OldrichKruchna you need to temporarily use the src/directives/bsSwitch.js from the develop branch, as the package is not on bower just yet.

from angular-bootstrap-switch.

Hi! Very cool module!
I wanted to note that I also face the same issue but under this circumstances. I open a modal with the use of angular-ui directives and pass some variables by using the resolve property in the modal configuration object. If I bind this to switch, then yes it still requires a first toggle on and off to start affecting ng-model value. However if i bind the switch to a local variable in the template, then the switch works immediately.
It also works If I bind the switch to a non existent property of the passed object. If the property already exists, it needs the first toggly cycle

** UPDATE: I found out actuallry that it doesn't matter that I pass any variable. The problem is when you try to bind ng-model to an existing property of an object. If the property exists, it needs the cycle. If not it works immediately

from angular-bootstrap-switch.

Any chance we can get this fix pushed to bower?

from angular-bootstrap-switch.

I am yet to solve more open issues since the rewrite in 0.4.0. I will release it as soon as possible.

from angular-bootstrap-switch.