Making some headway...
The base page is "Dashboard", which contains 10 panel components (each
having its own zone). Three of these panels require a "FilterPane" for
limiting the number of records displayed (again, this filter pane has its
own zone). This pane contains a form, and this form contains two
datefields.
After examining the application's log files I noticed that using the
datepicker resulted in the dashboard page's onActivate() method being
invoked. This was unexpected.
03-12-2018 12:02:40 DEBUG Dashboard:74 - [ENTER] onActivate(<EventContext:
movementZone>)
03-12-2018 12:02:40 DEBUG Dashboard:193 - onActivate
03-12-2018 12:02:40 INFO Dashboard:202 - User Chris [uid:3] accessed the
dashboard page
03-12-2018 12:02:40 DEBUG Dashboard:154 - [ EXIT] onActivate [null]
The above is the result of simply clicking on a date in the DatePicker popup.
At least part of the problem may be the way I've wired the 10 child panels
to the dashboard page itself (FilterPane is a grandchild).
>From the child template:
<a t:type="actionlink" async="true">...</a>
To the dashboard page class:
public void onActionFromOperationPanel(){
if(!expandedPanel.equals("operationZone")){
operationPanel.expand();
}
else{
operationPanel.collapse();
}
refreshZone("operationZone", operationZone);
}
The child component's actionlink obviously bubbles up to the dashboard
page's onActionFrom...() method. I'm not sure whether this is what's
triggering this page's onActivate() method, but hopefully I'm on the right
track.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
