basic DOM event handling
Michael Franklin <[email protected]> Mon, 18 Apr 2005 00:25:50 +0000 (UTC)
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Message-ID | <[email protected]> |
Ok, so I spotted the first bug in my code. The second argument to
__sig__.connect should reference the object that has the event handler.
Then I looked at what ta.onkeyup eval'd to:
function onkeyup(event) {
__sig__.emit(__components__.getComponentFromNode(this).checkExpand, this.value,
event); }
I thought onkeyPress might be a better candidate:
function onkeypress(event) {
__sig__.emit(__components__.getComponentFromNode(this).valueChange, this.value,
event); }
This suggested that I should make myTest() take some parameters. I read that if
the slot doesn't have the right number of parameters [determined by the signal]
it won't be called, right? So I tried 0,1,2 parameters, but still nothing.
Your help is appreciated.
Michael
_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org