NativeScript Angular2 Passing context parameter for data binding a function












0















I have been looking through the documentation and examples but cannot seem to find an appropriate example to pass the source entity to a function for binding.



For example, in trying to bind the "hidden" visibility parameter value to the result of function isHidden(), I would like to pass some sort of variable like callerContext that knows which TextField is is associated with the binding. Does such a variable exist or do I have create a scheme myself?



<TextField class="input" hint="Email address" [hidden]="isHidden(callerContext)"
keyboardType="email" autocorrect="false" autocapitalizationType="none"
[(ngModel)]="contactSettings.emailAddressList[0]" returnKeyType="next" (returnPress)="focusNext()">
</TextField>


Please let me know if this is not clear.










share|improve this question























  • These are the documentation for textfield in angular with nativescript. docs.nativescript.org/angular/ui/ng-ui-widgets/text-field docs.nativescript.org/api-reference/classes/… In your case for visibility you can use ng-if similar to here docs.nativescript.org/angular/ui/ng-ui-widgets/ng-directives

    – Baskar
    Nov 22 '18 at 5:18













  • Thanks for the references. I had read these. I was more looking for existence of some predefined source variables to link things together.

    – Jason
    Nov 22 '18 at 12:16
















0















I have been looking through the documentation and examples but cannot seem to find an appropriate example to pass the source entity to a function for binding.



For example, in trying to bind the "hidden" visibility parameter value to the result of function isHidden(), I would like to pass some sort of variable like callerContext that knows which TextField is is associated with the binding. Does such a variable exist or do I have create a scheme myself?



<TextField class="input" hint="Email address" [hidden]="isHidden(callerContext)"
keyboardType="email" autocorrect="false" autocapitalizationType="none"
[(ngModel)]="contactSettings.emailAddressList[0]" returnKeyType="next" (returnPress)="focusNext()">
</TextField>


Please let me know if this is not clear.










share|improve this question























  • These are the documentation for textfield in angular with nativescript. docs.nativescript.org/angular/ui/ng-ui-widgets/text-field docs.nativescript.org/api-reference/classes/… In your case for visibility you can use ng-if similar to here docs.nativescript.org/angular/ui/ng-ui-widgets/ng-directives

    – Baskar
    Nov 22 '18 at 5:18













  • Thanks for the references. I had read these. I was more looking for existence of some predefined source variables to link things together.

    – Jason
    Nov 22 '18 at 12:16














0












0








0








I have been looking through the documentation and examples but cannot seem to find an appropriate example to pass the source entity to a function for binding.



For example, in trying to bind the "hidden" visibility parameter value to the result of function isHidden(), I would like to pass some sort of variable like callerContext that knows which TextField is is associated with the binding. Does such a variable exist or do I have create a scheme myself?



<TextField class="input" hint="Email address" [hidden]="isHidden(callerContext)"
keyboardType="email" autocorrect="false" autocapitalizationType="none"
[(ngModel)]="contactSettings.emailAddressList[0]" returnKeyType="next" (returnPress)="focusNext()">
</TextField>


Please let me know if this is not clear.










share|improve this question














I have been looking through the documentation and examples but cannot seem to find an appropriate example to pass the source entity to a function for binding.



For example, in trying to bind the "hidden" visibility parameter value to the result of function isHidden(), I would like to pass some sort of variable like callerContext that knows which TextField is is associated with the binding. Does such a variable exist or do I have create a scheme myself?



<TextField class="input" hint="Email address" [hidden]="isHidden(callerContext)"
keyboardType="email" autocorrect="false" autocapitalizationType="none"
[(ngModel)]="contactSettings.emailAddressList[0]" returnKeyType="next" (returnPress)="focusNext()">
</TextField>


Please let me know if this is not clear.







angular data-binding binding nativescript






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 4:35









JasonJason

362711




362711













  • These are the documentation for textfield in angular with nativescript. docs.nativescript.org/angular/ui/ng-ui-widgets/text-field docs.nativescript.org/api-reference/classes/… In your case for visibility you can use ng-if similar to here docs.nativescript.org/angular/ui/ng-ui-widgets/ng-directives

    – Baskar
    Nov 22 '18 at 5:18













  • Thanks for the references. I had read these. I was more looking for existence of some predefined source variables to link things together.

    – Jason
    Nov 22 '18 at 12:16



















  • These are the documentation for textfield in angular with nativescript. docs.nativescript.org/angular/ui/ng-ui-widgets/text-field docs.nativescript.org/api-reference/classes/… In your case for visibility you can use ng-if similar to here docs.nativescript.org/angular/ui/ng-ui-widgets/ng-directives

    – Baskar
    Nov 22 '18 at 5:18













  • Thanks for the references. I had read these. I was more looking for existence of some predefined source variables to link things together.

    – Jason
    Nov 22 '18 at 12:16

















These are the documentation for textfield in angular with nativescript. docs.nativescript.org/angular/ui/ng-ui-widgets/text-field docs.nativescript.org/api-reference/classes/… In your case for visibility you can use ng-if similar to here docs.nativescript.org/angular/ui/ng-ui-widgets/ng-directives

– Baskar
Nov 22 '18 at 5:18







These are the documentation for textfield in angular with nativescript. docs.nativescript.org/angular/ui/ng-ui-widgets/text-field docs.nativescript.org/api-reference/classes/… In your case for visibility you can use ng-if similar to here docs.nativescript.org/angular/ui/ng-ui-widgets/ng-directives

– Baskar
Nov 22 '18 at 5:18















Thanks for the references. I had read these. I was more looking for existence of some predefined source variables to link things together.

– Jason
Nov 22 '18 at 12:16





Thanks for the references. I had read these. I was more looking for existence of some predefined source variables to link things together.

– Jason
Nov 22 '18 at 12:16












1 Answer
1






active

oldest

votes


















1














There won't be a variable named callerContext until you define one. If you want the textfield reference in isHidden method, then pass the textfield itself



<TextField #txt class="input" hint="Email address" [hidden]="isHidden(txt)" ....





share|improve this answer
























  • Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

    – Jason
    Nov 22 '18 at 12:17











  • Will work with this.

    – Jason
    Nov 22 '18 at 14:15













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423964%2fnativescript-angular2-passing-context-parameter-for-data-binding-a-function%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














There won't be a variable named callerContext until you define one. If you want the textfield reference in isHidden method, then pass the textfield itself



<TextField #txt class="input" hint="Email address" [hidden]="isHidden(txt)" ....





share|improve this answer
























  • Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

    – Jason
    Nov 22 '18 at 12:17











  • Will work with this.

    – Jason
    Nov 22 '18 at 14:15


















1














There won't be a variable named callerContext until you define one. If you want the textfield reference in isHidden method, then pass the textfield itself



<TextField #txt class="input" hint="Email address" [hidden]="isHidden(txt)" ....





share|improve this answer
























  • Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

    – Jason
    Nov 22 '18 at 12:17











  • Will work with this.

    – Jason
    Nov 22 '18 at 14:15
















1












1








1







There won't be a variable named callerContext until you define one. If you want the textfield reference in isHidden method, then pass the textfield itself



<TextField #txt class="input" hint="Email address" [hidden]="isHidden(txt)" ....





share|improve this answer













There won't be a variable named callerContext until you define one. If you want the textfield reference in isHidden method, then pass the textfield itself



<TextField #txt class="input" hint="Email address" [hidden]="isHidden(txt)" ....






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 '18 at 6:20









ManojManoj

6,3462922




6,3462922













  • Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

    – Jason
    Nov 22 '18 at 12:17











  • Will work with this.

    – Jason
    Nov 22 '18 at 14:15





















  • Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

    – Jason
    Nov 22 '18 at 12:17











  • Will work with this.

    – Jason
    Nov 22 '18 at 14:15



















Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

– Jason
Nov 22 '18 at 12:17





Ok, that is what I found so far. I was hoping to avoid naming individual fields and then passing that same name since it is so redundant and error prone. Thanks for clarifying.

– Jason
Nov 22 '18 at 12:17













Will work with this.

– Jason
Nov 22 '18 at 14:15







Will work with this.

– Jason
Nov 22 '18 at 14:15






















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53423964%2fnativescript-angular2-passing-context-parameter-for-data-binding-a-function%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

Npm cannot find a required file even through it is in the searched directory