[ 
https://issues.apache.org/jira/browse/PIVOT-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piotr Kołaczkowski closed PIVOT-808.
------------------------------------

    Resolution: Duplicate

Duplicate of bug 768.
                
> Components spanning more than one column in the TablePane do not receive 
> mouse events properly
> ----------------------------------------------------------------------------------------------
>
>                 Key: PIVOT-808
>                 URL: https://issues.apache.org/jira/browse/PIVOT-808
>             Project: Pivot
>          Issue Type: Bug
>          Components: wtk
>    Affects Versions: 2.0.1
>         Environment: Java 1.6.0. update 26 and 1.7.0 update 2 build 08
> OS: Windows 7 64-bit or Kubuntu 11.10
>            Reporter: Piotr Kołaczkowski
>              Labels: Filler, TablePane, TablePane.columnSpan, events
>
> I've got a table row like that:
> <TablePane.Row height="1*">
>             <Label text="Trig" 
> styles="{font:{bold:true},verticalAlignment:'center'}"/>
>             <ListButton bxml:id="triggerSource" 
> listData="['Off','CH1','CH2']" selectedItem="Off"/>
>             <ListButton bxml:id="triggerSlope" TablePane.columnSpan="2" 
> listData="['Up','Down']" selectedItem="Up"/>
>             <TablePane.Filler/>
>             <Label text="Holdoff" 
> styles="{verticalAlignment:'center',horizontalAlignment:'right'}"/>
>             ...
> </TablePane.Row>
> The "triggerSlope" list button spans two columns. If you click the mouse on 
> the point that belongs to the first spanned column (the third column in this 
> example), the list expads and you can select an option. But if you click the 
> point that belongs to the second spanned column (the fourth column, i.e. this 
> column where the Filler is), there is no reaction. It seems that the mouse 
> click goes to the Filler instead of the component. This is especially nasty 
> for ListButtons, because their arrow is near the right edge, and this poses a 
> serious usability problem.
> Until it is fixed, can you give me a workaround for this? 
> Affects version: 2.0.1. revision 1187295  (fresh source checked out today 
> from SVN)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to