NativeScript core TextField onTextChange in model and outside model
up vote
0
down vote
favorite
I´m using NativeScript 5.0 core and it seems that there's no method to do textChange events on textfields. My idea is something like this:
<TextField class="width90" text="{{ productPrize }}" editable="true" textChange="{{ onTexTextChange }}"/>
and in js side:
exports.onReSonTexTextChangecanPrize = function (args) {
alert(test);
};
this sintax works fine for me in "tap" events, but i read something like there's no method for doing that o NativeScript core 5.0.
I found a method in NativeScript doc doing this stuff in module:
const observableModule = require("tns-core-modules/data/observable");
function HomeViewModel() {
const viewModel = observableModule.fromObject({
productCode: "",
productPrize: ""
});
viewModel.addEventListener(observableModule.Observable.propertyChangeEvent, (args) => {
// args is of type PropertyChangeData
console.log("propertyChangeEvent [eventName]: ", args.eventName);
console.log("propertyChangeEvent [propertyName]: ", args.propertyName);
console.log("propertyChangeEvent [value]: ", args.value);
console.log("propertyChangeEvent [oldValue]: ", args.oldValue);
console.log("propertyChangeEvent [object]: ", args.object);
});
return viewModel;
}
module.exports = HomeViewModel;
I'm getting the logs correctly, but I don't know how to export the correspondant value to the model.
I have this code for conecting to the view:
const HomeViewModel = require("./home-view-model");
exports.onNavigatingTo = function(args) {
page = args.object;
mv = page.bindingContext = new HomeViewModel();
};
I wanted to know how can I do this like the example, but it will be interesting to know how could it be developed on module too.
javascript events nativescript
asked Nov 22 at 14:42
Noark
79112
add a comment |
up vote
0
down vote
favorite
I´m using NativeScript 5.0 core and it seems that there's no method to do textChange events on textfields. My idea is something like this:
<TextField class="width90" text="{{ productPrize }}" editable="true" textChange="{{ onTexTextChange }}"/>
and in js side:
exports.onReSonTexTextChangecanPrize = function (args) {
alert(test);
};
this sintax works fine for me in "tap" events, but i read something like there's no method for doing that o NativeScript core 5.0.
I found a method in NativeScript doc doing this stuff in module:
const observableModule = require("tns-core-modules/data/observable");
function HomeViewModel() {
const viewModel = observableModule.fromObject({
productCode: "",
productPrize: ""
});
viewModel.addEventListener(observableModule.Observable.propertyChangeEvent, (args) => {
// args is of type PropertyChangeData
console.log("propertyChangeEvent [eventName]: ", args.eventName);
console.log("propertyChangeEvent [propertyName]: ", args.propertyName);
console.log("propertyChangeEvent [value]: ", args.value);
console.log("propertyChangeEvent [oldValue]: ", args.oldValue);
console.log("propertyChangeEvent [object]: ", args.object);
});
return viewModel;
}
module.exports = HomeViewModel;
I'm getting the logs correctly, but I don't know how to export the correspondant value to the model.
I have this code for conecting to the view:
const HomeViewModel = require("./home-view-model");
exports.onNavigatingTo = function(args) {
page = args.object;
mv = page.bindingContext = new HomeViewModel();
};
I wanted to know how can I do this like the example, but it will be interesting to know how could it be developed on module too.
javascript events nativescript
asked Nov 22 at 14:42
Noark
79112
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I´m using NativeScript 5.0 core and it seems that there's no method to do textChange events on textfields. My idea is something like this:
<TextField class="width90" text="{{ productPrize }}" editable="true" textChange="{{ onTexTextChange }}"/>
and in js side:
exports.onReSonTexTextChangecanPrize = function (args) {
alert(test);
};
this sintax works fine for me in "tap" events, but i read something like there's no method for doing that o NativeScript core 5.0.
I found a method in NativeScript doc doing this stuff in module:
const observableModule = require("tns-core-modules/data/observable");
function HomeViewModel() {
const viewModel = observableModule.fromObject({
productCode: "",
productPrize: ""
});
viewModel.addEventListener(observableModule.Observable.propertyChangeEvent, (args) => {
// args is of type PropertyChangeData
console.log("propertyChangeEvent [eventName]: ", args.eventName);
console.log("propertyChangeEvent [propertyName]: ", args.propertyName);
console.log("propertyChangeEvent [value]: ", args.value);
console.log("propertyChangeEvent [oldValue]: ", args.oldValue);
console.log("propertyChangeEvent [object]: ", args.object);
});
return viewModel;
}
module.exports = HomeViewModel;
I'm getting the logs correctly, but I don't know how to export the correspondant value to the model.
I have this code for conecting to the view:
const HomeViewModel = require("./home-view-model");
exports.onNavigatingTo = function(args) {
page = args.object;
mv = page.bindingContext = new HomeViewModel();
};
I wanted to know how can I do this like the example, but it will be interesting to know how could it be developed on module too.
javascript events nativescript
asked Nov 22 at 14:42
Noark
79112
I´m using NativeScript 5.0 core and it seems that there's no method to do textChange events on textfields. My idea is something like this:
<TextField class="width90" text="{{ productPrize }}" editable="true" textChange="{{ onTexTextChange }}"/>
and in js side:
exports.onReSonTexTextChangecanPrize = function (args) {
alert(test);
};
this sintax works fine for me in "tap" events, but i read something like there's no method for doing that o NativeScript core 5.0.
I found a method in NativeScript doc doing this stuff in module:
const observableModule = require("tns-core-modules/data/observable");
function HomeViewModel() {
const viewModel = observableModule.fromObject({
productCode: "",
productPrize: ""
});
viewModel.addEventListener(observableModule.Observable.propertyChangeEvent, (args) => {
// args is of type PropertyChangeData
console.log("propertyChangeEvent [eventName]: ", args.eventName);
console.log("propertyChangeEvent [propertyName]: ", args.propertyName);
console.log("propertyChangeEvent [value]: ", args.value);
console.log("propertyChangeEvent [oldValue]: ", args.oldValue);
console.log("propertyChangeEvent [object]: ", args.object);
});
return viewModel;
}
module.exports = HomeViewModel;
I'm getting the logs correctly, but I don't know how to export the correspondant value to the model.
I have this code for conecting to the view:
const HomeViewModel = require("./home-view-model");
exports.onNavigatingTo = function(args) {
page = args.object;
mv = page.bindingContext = new HomeViewModel();
};
I wanted to know how can I do this like the example, but it will be interesting to know how could it be developed on module too.
javascript events nativescript
javascript events nativescript
asked Nov 22 at 14:42
Noark
79112
asked Nov 22 at 14:42
Noark
79112
asked Nov 22 at 14:42
Noark
79112
asked Nov 22 at 14:42
Noark
79112
asked Nov 22 at 14:42
Noark
79112
79112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Finally I found a method, but I don't know if it's a "clean" solution or if there is a better solution:
page.getViewById("texFieldId").addEventListener("textChange", function(args){
console.log("text changed");
})
answered Nov 22 at 15:39
Noark
79112
1
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
add a comment |
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',
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433333%2fnativescript-core-textfield-ontextchange-in-model-and-outside-model%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
up vote
0
down vote
accepted
Finally I found a method, but I don't know if it's a "clean" solution or if there is a better solution:
page.getViewById("texFieldId").addEventListener("textChange", function(args){
console.log("text changed");
})
answered Nov 22 at 15:39
Noark
79112
1
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
add a comment |
up vote
0
down vote
accepted
Finally I found a method, but I don't know if it's a "clean" solution or if there is a better solution:
page.getViewById("texFieldId").addEventListener("textChange", function(args){
console.log("text changed");
})
answered Nov 22 at 15:39
Noark
79112
1
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Finally I found a method, but I don't know if it's a "clean" solution or if there is a better solution:
page.getViewById("texFieldId").addEventListener("textChange", function(args){
console.log("text changed");
})
answered Nov 22 at 15:39
Noark
79112
Finally I found a method, but I don't know if it's a "clean" solution or if there is a better solution:
page.getViewById("texFieldId").addEventListener("textChange", function(args){
console.log("text changed");
})
answered Nov 22 at 15:39
Noark
79112
answered Nov 22 at 15:39
Noark
79112
answered Nov 22 at 15:39
Noark
79112
answered Nov 22 at 15:39
Noark
79112
79112
1
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
add a comment |
1
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
1
1
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
That's the solution, property change events doesn't work from XML.
– Manoj
Nov 22 at 15:43
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
perfect, lots of thanks. that confirmation helps me a lot.
– Noark
Nov 22 at 15:53
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433333%2fnativescript-core-textfield-ontextchange-in-model-and-outside-model%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
