Yup, an entirely new controller gets created whenever you switch templates.
If you need data to persist over multiple templates, it's best to use a
factory to manage this.
On Monday, April 21, 2014 11:30:29 AM UTC-7, Rafael Wolf wrote:
>
> Hello guys...
>
> I'm trying to use a controller with many templates, a simple CRUD, Index,
> Edit and Create.
>
> And the controller is setted by routeProvider, like this:
>
> * .when('/tipocontato', { templateUrl: '/tipocontato/index',
> controller: 'TipoContatoController' })*
> * .when('/tipocontato/create', { templateUrl:
> '/tipocontato/create', controller: 'TipoContatoController' })*
> * .when('/tipocontato/edit', { templateUrl:
> '/tipocontato/edit', controller: 'TipoContatoController' })*
>
> But when i change de route, controller seems be recreated.
>
> It is correct ?
>
> And use the same controller with many templates, it is correct to ?
>
> Thanks!
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
