Hello Sebastien,
Sorry, it was my fault. I didn't explain correctly my problem.
Thank you for your clarification.
I don't want to modify the fullcalendar's behavior .
I bypassed the problem.
I directly concatenated the *title *with the *name * of the identifiant (
in a nice phrase ) .
Hi sebastien,
Thanks for the reply.
Yes I called calendar.refresh(target) and I use a CompoundPropertyModel.
May be i did not use these the right way?
I called also calendar.modelChanged() after the form submit but still the
same behavoir.
Please see my attached quick start zip.
Best
Hi Pierre,
Thanks for the attached zip. I do not see weird things that can prevent the
autocomplete to reflect the changed model object.
Unfortunately, I am not able to debug the quickstart because it missing to
much dependencies (Joda, Spring...) and custom classes (AgendaModele,
AmemetTemplate,
Sebastien,
Thank for your suggestion.
My bean (PersonnelEvent ) is correctely persisted after submiting the
dialog.
Also I did the debugging.
And it seems like the problem is due to the fact that my field sesame is
not a *Event Data* field from fullCalendar
Hi Pierre,
I have misunderstood the issue, sorry. I thought you had something
displayed before (state #1), which was not reflected after the update
(state #2)...
Actually, the visual representation of the event in the calendar relies on
the calendar itself (fullcalendar.js). If you wish to
Hi all,
I am currently based on the
com.googlecode.wicket.jquery.ui.samples.pages.calendar.ExtendedCalendarPage
I have added in my dialog panel (AbstractFormDialog) another field ( an
identifiant in a
wicket.jquery.ui..AutoCompleteTextFieldString(identifiant) ).
The event model looks like
Hi Pierre,
Did you called calendar.refresh(target)?
Do you use a CompoundPropertyModel? Maybe you have to call
calendar#modelChanged?
Can you post a quickstart so I can investigate?
Thanks in advance,
Sebastien.
On Fri, Jan 10, 2014 at 4:45 PM, Selom pierre.kou...@uhb.fr wrote:
Hi all,
I
