Changes between Version 5 and Version 8 of Ticket #3214


Ignore:
Timestamp:
May 5, 2011, 7:02:17 AM (9 years ago)
Author:
bill
Comment:

Hmm, well

StackContainer.watch("selectedChild", function(name, o, n){ ... })

will tell you the old child and the new child, but it's not exactly the same since the timing probably happens after the transition is complete.

I'm moving away from the subscribe/publish model for notification, but consider adding a notificatication like

StackContainer.on("unselect-child", ...)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3214

    • Property Owner changed from Adam Peller to bill
    • Property Summary changed from enhancement request:: page container should publish an event for unselect to StackContainer: publish event for unselect
  • Ticket #3214 – Description

    v5 v8  
    11Hi dojo team,
    22
    3 Two enhancement proposal regarding PageContainer
     3Two enhancement proposal regarding !StackContainer:
    44
    5 First idea:
    6 ----------
    7 when the 'selectChild' method of PageContainer is called, the following event is pusblished:
     5'''First idea:'''
     6
     7when the 'selectChild' method of !StackContainer is called, the following event is published:
     8
    89                dojo.event.topic.publish(this.widgetId+"-selectChild", page);
    910
     
    1213                dojo.event.topic.publish(this.widgetId+"-unselectChild", this.selectedChildWidget);
    1314
    14 This would allow the developper to take action such as stopping a timer, or changing the focus...
    15 ===================
    16 Second idea
    17 -----------
     15This would allow the developer to take action such as stopping a timer, or changing the focus...
     16
     17
     18'''Second idea:'''
     19
    1820Another idea would be to programmatically be able to reject the request to change the current page is some condition is not met (data not saved...)
    1921