You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Gerolf Seitz (JIRA)" <ji...@apache.org> on 2007/06/18 00:47:25 UTC
[jira] Created: (WICKET-661) fire onchange event of associated
component after date selection
fire onchange event of associated component after date selection
----------------------------------------------------------------
Key: WICKET-661
URL: https://issues.apache.org/jira/browse/WICKET-661
Project: Wicket
Issue Type: Improvement
Components: wicket-datetime
Affects Versions: 1.3.0-beta1
Reporter: Gerolf Seitz
Priority: Minor
sometimes it's desirable to be notified after a date was selected.
therefore the change event (onchange() method) of the associated component should be fired.
to not break existing code, a second constructor should be added to specify whether the event should be fired, whereas the default behavior is to not fire the event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-661) fire onchange event of associated
component after date selection
Posted by "Gerolf Seitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerolf Seitz updated WICKET-661:
--------------------------------
Attachment: fire_onchange.patch
> fire onchange event of associated component after date selection
> ----------------------------------------------------------------
>
> Key: WICKET-661
> URL: https://issues.apache.org/jira/browse/WICKET-661
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-datetime
> Affects Versions: 1.3.0-beta1
> Reporter: Gerolf Seitz
> Priority: Minor
> Attachments: fire_onchange.patch
>
>
> sometimes it's desirable to be notified after a date was selected.
> therefore the change event (onchange() method) of the associated component should be fired.
> to not break existing code, a second constructor should be added to specify whether the event should be fired, whereas the default behavior is to not fire the event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WICKET-661) fire onchange event of associated
component after date selection
Posted by "Gerolf Seitz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerolf Seitz closed WICKET-661.
-------------------------------
> fire onchange event of associated component after date selection
> ----------------------------------------------------------------
>
> Key: WICKET-661
> URL: https://issues.apache.org/jira/browse/WICKET-661
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-datetime
> Affects Versions: 1.3.0-beta1
> Reporter: Gerolf Seitz
> Assignee: Eelco Hillenius
> Priority: Minor
> Fix For: 1.3.0-beta3
>
> Attachments: fire_onchange.patch
>
>
> sometimes it's desirable to be notified after a date was selected.
> therefore the change event (onchange() method) of the associated component should be fired.
> to not break existing code, a second constructor should be added to specify whether the event should be fired, whereas the default behavior is to not fire the event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-661) fire onchange event of associated
component after date selection
Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eelco Hillenius resolved WICKET-661.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0-beta3
I changed it a little bit, so that it uses an overridable method (notifyComponentOnDateSelected) rather than a member variable. It's a bit cheaper on memory like that.
> fire onchange event of associated component after date selection
> ----------------------------------------------------------------
>
> Key: WICKET-661
> URL: https://issues.apache.org/jira/browse/WICKET-661
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-datetime
> Affects Versions: 1.3.0-beta1
> Reporter: Gerolf Seitz
> Assignee: Eelco Hillenius
> Priority: Minor
> Fix For: 1.3.0-beta3
>
> Attachments: fire_onchange.patch
>
>
> sometimes it's desirable to be notified after a date was selected.
> therefore the change event (onchange() method) of the associated component should be fired.
> to not break existing code, a second constructor should be added to specify whether the event should be fired, whereas the default behavior is to not fire the event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-661) fire onchange event of associated
component after date selection
Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eelco Hillenius reassigned WICKET-661:
--------------------------------------
Assignee: Eelco Hillenius
> fire onchange event of associated component after date selection
> ----------------------------------------------------------------
>
> Key: WICKET-661
> URL: https://issues.apache.org/jira/browse/WICKET-661
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-datetime
> Affects Versions: 1.3.0-beta1
> Reporter: Gerolf Seitz
> Assignee: Eelco Hillenius
> Priority: Minor
> Attachments: fire_onchange.patch
>
>
> sometimes it's desirable to be notified after a date was selected.
> therefore the change event (onchange() method) of the associated component should be fired.
> to not break existing code, a second constructor should be added to specify whether the event should be fired, whereas the default behavior is to not fire the event.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.