Hi,
Sorry I've been away for a few days hence the lack of reply. Inge, I tried
to explain my problem carefully and precisely as Igor indicated that he
didn't understand it. Of course my problem doesn't make sense, if it made
sense I could solve it and it wouldn't be a problem! Feel free to
Thanks for your reply Howard. Are you suggesting that I need to add this
onSuccess method to my confirmation page as well as keeping it in the
layout?
Howard Lewis Ship wrote:
When an event bubbles up, the origin of the event changes.
Initially, the success event occurs from the form
Hi Igor,
I thought i'd spelled out this issue fairly clearly, but here goes again.
All of my pages use a layout along these lines:
http://tapestry.apache.org/tapestry5/guide/layout.html
Inside this component I have a login form. This login form works on all
pages, except for a specific page
I think what Howard said was that your FromQuestionForm part won't work,
since the origin changes when the event bubbles up. Change the name to
onSuccess and see if gets called then.
On Tue, Jan 5, 2010 at 10:47 AM, lebenski be...@gamesys.co.uk wrote:
Hi Igor,
I thought i'd spelled out this
This isn't the form I'm having trouble with. The Submit a Question form
works fine.
The form that is not working is the LoginForm in the layout. Using
onSuccessFromLoginForm works in all other pages except the confirmation
page. Are you suggesting that I should change the method in my
I only suggested it for testing to see if it gets called. If it gets called,
it means that the origin changed, and your FromXXX must be changed.
On Tue, Jan 5, 2010 at 11:23 AM, lebenski be...@gamesys.co.uk wrote:
This isn't the form I'm having trouble with. The Submit a Question form
works
Ok I think I'm missing something because I don't understand why this would
happen.
If I have two pages:
Page1.tml
t:layout
Page 1 Goes Here
/t:layout
Page2.tml
t:layout
Page 2 Goes Here
/t:layout
And a layout...
Layout.tml (simplified)
html
body
t:form t:id=hello
...form content
I don't know. What I DO know is this:
Trying hard to explain why your problem doesn't make sense is not a very
good way of solving it. I do that very often, and I'm always corrected by
someone who asks the obvious questions ;)
The best way is to binary search your way through this, by modifying
No way to find out the triggering component that I'm aware of.
Incidentally, the original poster is incorrect regarding changing
onSuccessFromXXX to onSuccess. In T5, events only ever bubble up,
never back down. So it's true that onSuccess within the layout
component will handle any
I have a layout component that contains a login form:
t:form t:id=loginForm
t:textfield t:id=loginUsernameField t:value=memberName
height=30/
t:passwordfield t:id=loginPasswordField t:value=password /
t:submit id=loginSubmit value=message:login/
/t:form
Page Class:
Your explanation is unclear. This way you never get an answer. Please be
more precise and post more of your code.
On Mon, Jan 4, 2010 at 11:07 AM, lebenski be...@gamesys.co.uk wrote:
I have a layout component that contains a login form:
t:form t:id=loginForm
t:textfield
When an event bubbles up, the origin of the event changes.
Initially, the success event occurs from the form inside the layout component.
If the event is not handled there, it becomes a success event *from
the layout component* (at the page).
On Mon, Jan 4, 2010 at 12:11 PM, Igor Drobiazko
12 matches
Mail list logo
