Hmmm I'm not sure completely. If you had an example I can play with more
easily attached to a jira issue I can take a look.
On 6/28/07, Julian Wood <[EMAIL PROTECTED]> wrote:
Well I'll look forward to the time when that's implemented! But I'm
still curious what the problem is with my origina
Well I'll look forward to the time when that's implemented! But I'm
still curious what the problem is with my original approach, as it
seems to be a different problem. That is, after an initial async
submission, the eventlistener invokes the listener on the submit
button when it shouldn't.
Haha look at that. I forget that it can bind to any function sometimes.
That's neat. :)
Yes that was what I was thinking as the "strategy" for doing EventListener
connections on this specific type of component. It would need to honor any
existing informal onclick attributes and back off to
I used a little trick to get the radiobuttons to send an event, which
I suppose could be the problem. All you need to do is add this
onclick handler to each radio button, and then the tapestry event
listener will respond.
value="ognl:@[EMAIL PROTECTED]" onclick="document.getElementB
I've made a sample application, as simply as I could, to show the
problem. I've put it on my blog if anyone is interested in looking.
http://jwoodchip.blogspot.com/2007/06/event-listener-oddities.html
Thanks,
J
On 26-Jun-07, at 10:45 PM, Marcus Schulte wrote:
That should really work. I'm us
EventListener && Radio Groups don't really get along so well. The reason
being that each radio group button must have the same name attribute and
there is no dom equivalent of a select->options wrapper around them.
It's possible that ~something~ can be done for this but I'm not sure of what
that
That should really work. I'm using something very similar (checkbox instead
of radiobutton). If you post some code, I can look for differences.
2007/6/27, Julian Wood <[EMAIL PROTECTED]>:
I have a pretty straight forward paradigm:
- two groups of 3 radio buttons followed by a property selecti
I have a pretty straight forward paradigm:
- two groups of 3 radio buttons followed by a property selection.
- an async form with no listener whatsoever
- a submit button with an action listener (called saveTime)
The idea is that choosing a radio button narrows down the list in the
property se
