[
https://issues.apache.org/jira/browse/PIVOT-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858875#action_12858875
]
Greg Brown commented on PIVOT-458:
----------------------------------
> Can't. I'm not assigned to the Pivot project, so the JIRA workflow won't let
> me assign myself.
I just added you as a Contributor, so you should be able to assign the issue to
yourself now.
> If split mode is on, pressing the triangle shows the pressed state on the
> _whole button_, not the triangle part only, because otherwise it looks
> strange.
Interesting. For reference, I just looked at the ExtJS split button to see how
it behaves. It does not paint a different state depending on where the user
clicks, so I couldn't get a sense for what this looks like. I also looked for a
Silverlight example but I couldn't find one. Any idea how the Windows split
button handles this?
> ListButton: show popup only on triangle click
> ---------------------------------------------
>
> Key: PIVOT-458
> URL: https://issues.apache.org/jira/browse/PIVOT-458
> Project: Pivot
> Issue Type: Improvement
> Components: wtk-terra
> Reporter: Dirk Moebius
> Priority: Minor
> Fix For: 1.5
>
> Attachments: listbutton-popup.patch, menubutton-popup.patch
>
>
> I found this to be a requirement in my application: if the user clicks the
> label part of a LinkButton, the button should fire immediately without
> showing the popup, thus invoking the action with the currently selected
> entry. If the user clicks the triangle part, the popup should be shown.
> I patched LinkButton to add a new boolean property called
> "showPopupOnTriggerClickOnly" to TerraListButtonSkin (I couldn't think of a
> better name, sorry). If set to true, the ListButton popup will only show up
> if the user clicks the triangle, but not if the user clicks the rest of the
> button. However, ButtonPressListeners fire as usual, if the user clicks any
> part of the button. If the property is false, the behavior is as it was
> before. The default value of the property is false.
> I tested the patch in my application and ComponentExplorer and it works good.
> It would be nice if you integrate the patch. Otherwise I'd still have the
> option to write a custom skin, but I think this patch could be interesting to
> other developers as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
