<br><br><div class="gmail_quote">On Tue, Jun 10, 2008 at 2:30 PM, Eben Eliason <<a href="mailto:eben.eliason@gmail.com">eben.eliason@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Actually, I disagree with adding "Start" separately to the secondary<br> palette as this will appear redundant beneath the already existing<br> "Start" label in the primary palette.  The better solution (and I<br> think, the expected behavior) is to make the primary palette clickable<br> when the palette is anchored, such that clicking it enacts the action<br> of the button it is attached to.</blockquote><div><br>I agree that this is how palettes should work (of course, not the issue here).<br><br>However, I don't understand your opposition to repeating the "start" option in the submenu. Any journal item already repeats the default option in this list; doing the same for activity bundles is only consistent. If we are going to change this, it is a separate patch.<br>  </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br> <br> Regarding the other options, I think it would be clearer (albeit,<br> admittedly, slightly more indirect) to place the list of available<br> activities in a submenu labeled "Start with" to convey the action that<br> selecting an activity will take.  This would be true of the submenu<br> regardless of whether or not the entry represents a bundle, leaving us<br> in a state where the only difference between bundles and instances is<br> the phrasing used within the menu.  Otherwise, they are functionally<br> identical.</blockquote><div><br>This is not a bad idea. Again, if you are serious about this, we should prioritize it and do it, as a separate patch; and I'd be happy to work through the options with you, in a separate thread.<br> <br>Jameson<br></div></div><br>