I tried with following
I made two new Params kopijaDatum and kopijaBroj.
I made one function
onPrepareForSubmit(){
and set initialization here
kopijaDatum= datum;
kopijaBroj = broj;
}
but I get same result eventhough I think this should work just fine.
> From: wintertime0...@outlook.com
> To: users@tapestry.apache.org
> Subject: RE: Calling property in t:message
> Date: Sat, 18 Oct 2014 02:52:46 +0100
>
> Hey Geoff!
> Yes, data flow is just OK. However only trouble with this is that I can't see
> ${broj} and ${datum} values as taken from input fields on Confirm dialog.
> Instead of their real values I see only 0 and null, because I initialized
> them as such( well, only datum parameter ) ( this behavior is because I set
> them only after I press OK on Confirm dialog ).
>
> > Subject: Re: Calling property in t:message
> > From: geoff.callender.jumpst...@gmail.com
> > Date: Sat, 18 Oct 2014 12:45:12 +1100
> > To: users@tapestry.apache.org
> >
> > The flow gets up to displaying a dialog. Should the dialog show any data
> > values? Which ones? What is the intended flow after choosing Confirm? What
> > is the intended flow after choosing Not Confirm (ok, this one's not hard to
> > guess).
> >
> > On 18 Oct 2014, at 12:40 pm, Name Surname <wintertime0...@outlook.com>
> > wrote:
> >
> > > Hi, Geoff! :)
> > >
> > > Normal flow would be that user submits a form, and Confirm dialog
> > > appears in which he can then confirm or not confirm. It's working just
> > > fine, however I can't see ${broj} and ${datum} with real values as they
> > > are but 0 and null, since calling of a function onSubmit( which sets up
> > > our broj and datum fields ) is only processed after I click OK on cofirm
> > > ( however in order for me to see what value I want to create, I would
> > > need ${broj} to be set ( taken from input ) on Confirm dialog.
> > >
> > > P.S. Check your message.
> > >
> > >> Subject: Re: Calling property in t:message
> > >> From: geoff.callender.jumpst...@gmail.com
> > >> Date: Sat, 18 Oct 2014 11:51:47 +1100
> > >> To: users@tapestry.apache.org
> > >>
> > >> Hey Name Surname, we see your code but can only guess at the behaviour
> > >> you want it to exhibit. Perhaps you could describe the intended "normal
> > >> flow", and then describe the intended "exception flows".
> > >>
> > >> On 18 Oct 2014, at 3:45 am, Name Surname <wintertime0...@outlook.com>
> > >> wrote:
> > >>
> > >>> Hey Lance. I have just seen this example. It's looking great, however
> > >>> how can I make it operable on my example?
> > >>> operable on my example?
> > >>>
> > >>>> Date: Fri, 17 Oct 2014 15:34:40 +0100
> > >>>> Subject: RE: Calling property in t:message
> > >>>> From: lance.j...@googlemail.com
> > >>>> To: users@tapestry.apache.org
> > >>>>
> > >>>> If you want to pass clientside values in an event, the observe mixin
> > >>>> can
> > >>>> help
> > >>>> http://tapestry-stitch.uklance.cloudbees.net/observedemo
> > >>>>
> > >>>> Note: This has prototype specific code that needs to be translated to
> > >>>> jquery
> > >>>> On 17 Oct 2014 04:57, "Name Surname" <wintertime0...@outlook.com>
> > >>>> wrote:
> > >>>>
> > >>>>> Hey Thiago! :)
> > >>>>>
> > >>>>> Well the reason why I can't set the freaking fields is because it's
> > >>>>> only
> > >>>>> input on clients side, and onSuccess function is called only after I
> > >>>>> press
> > >>>>> Confirm from JQuery/Confirm mixin. So I have very odd situation here,
> > >>>>> can't
> > >>>>> back, can't ahead...
> > >>>>>
> > >>>>> I press Confirm and I get opened Confirm dialog. But because values
> > >>>>> here
> > >>>>> aren't yet set( they are waiting for Submit from the Confirm dialog)
> > >>>>> I get
> > >>>>> those values as null and 0. Can you propose me how to get rid of this
> > >>>>> situation.
> > >>>>>
> > >>>>>> To: users@tapestry.apache.org
> > >>>>>> Subject: Re: Calling property in t:message
> > >>>>>> Date: Thu, 16 Oct 2014 09:17:18 -0300
> > >>>>>> From: thiag...@gmail.com
> > >>>>>>
> > >>>>>> On Wed, 15 Oct 2014 20:55:40 -0300, Name Surname
> > >>>>>> <wintertime0...@outlook.com> wrote:
> > >>>>>>
> > >>>>>>> Hi Thiago! :)
> > >>>>>>> Aha, I understand now request concept. However, how can I make this
> > >>>>>>> work? Can you give me some directions?
> > >>>>>>
> > >>>>>> Besides "set the freaking fields! :D", I have nothing else to offer,
> > >>>>>> because I don't know what logic you want to implement. Anyway,
> > >>>>>> that's up
> > >>>>>> to you. @Persist persists field values between requests, but *you*
> > >>>>>> need
> > >>>>> to
> > >>>>>> set these values first. So far, for one field, you never give it a
> > >>>>>> value.
> > >>>>>> For the other, you always set it to null. Tapestry is doing exactly
> > >>>>>> what
> > >>>>>> you're asking it to do.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Thiago H. de Paula Figueiredo
> > >>>>>> Tapestry, Java and Hibernate consultant and developer
> > >>>>>> http://machina.com.br
> > >>>>>>
> > >>>>>> ---------------------------------------------------------------------
> > >>>>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > >>>>>> For additional commands, e-mail: users-h...@tapestry.apache.org
> > >>>>>>
> > >>>>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > >> For additional commands, e-mail: users-h...@tapestry.apache.org
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
>
