Thank you again Lance!
Thats exactly what I need.
Regards,
Matias.
On Wed, Jun 27, 2012 at 11:34 PM, Matías Blasi wrote:
> Thank you Lance!
>
> This seems to be useful, but as far as I understand, it couldn't be
> possible to handle single Alert dismission, right?
>
> Regards,
> Matias.
>
>
>
/ApplicationStateContribution.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/How-to-know-when-an-Alert-is-dismissed-tp5714120p5714136.html
Sent from the Tapestry - User mailing list archive at Nabble.com
Thank you Lance!
This seems to be useful, but as far as I understand, it couldn't be
possible to handle single Alert dismission, right?
Regards,
Matias.
On Wed, Jun 27, 2012 at 6:03 PM, Matías Blasi wrote:
> Hi, I recently upgraded to tapestry-5.3.3, and I am trying to replace my
> own user-me
Tapestry published the "tapestry:dismiss-all" event when the alerts are
dismissed.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/How-to-know-when-an-Alert-is-dismissed-tp5714120p5714123.html
Sent from the Tapestry - User mailing list archive at
Hi, I recently upgraded to tapestry-5.3.3, and I am trying to replace my
own user-messages component with the great Alerts one.
My problem is that I need to know when a UNTIL_DISMISSED Alert is
dismissed. It is because I mark it as read in a database, because the
Alerts are generated for the users
