[ 
https://issues.apache.org/jira/browse/PIVOT-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858902#action_12858902
 ] 

Greg Brown commented on PIVOT-458:
----------------------------------

Right - the "open" state draws the popup as if it was attached to the button, 
which is nice. However, that's probably beyond the scope of what we need to do 
for now. We are generally deferring significant L&F changes to v2.0 or later, 
when we plan to invest time in doing a full overhaul of the UI.

If the current version works for you, my vote would be to leave it as-is for 
now.

Nice work - thanks for the submission.


> 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, 
> office-listbutton-hovered.png, office-listbutton-normal.png, 
> office-listbutton-pressed.png, office-listbutton-triggerclicked.png
>
>
> 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.

Reply via email to