Double clicking on the right arrow give the same result as clicking the left arrow. Furthermore, selecting an entry in the left pane and clicking on the left arrow twice in a row will put the selected entry in the right pane and back in the left one. (So that the second clic, although not a double clic since the selection has changed between the first and second clic, acts as a clic on the left arrow.

Pierre-Yves

Igor Vaynberg a écrit :
fixed

-Igor


On 5/31/06, *cowwoc* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:


            There seems to be a bug in this example. I select the last
    entry, and
    keep on clicking on the first button. Eventually, it moves the entry
    from the right side to the left, even though I am clicking on the arrow
    pointing from left to right. I am expecting the entry to remain on the
    right. Can anyone else reproduce this?

    Gili

    Philip A. Chapman wrote:
     > The palette component:
     >
     >
    
http://www.wicket-library.com/wicket-examples/compref;jsessionid=1964CEEDBD5270FCDA54CFE3AFAE4CB7?wicket:bookmarkablePage=:wicket.examples.compref.PalettePage
     >
     > On Wed, 2006-05-31 at 23:32 -0300, Bruno Borges wrote:
     >> I don't know how to name it, but "Shuttle" was the name I've seen
     >> people using to specify this kind of component:
     >>
     >>  ________        ________
     >> | Item 1 |  >>  | Item 3 |
     >> | Item 2 |  >   | Item 4 |
     >> |        |      |        |
     >> |        |  <   |        |
     >> |________|  <<  |________|
     >>
     >>
     >> Where:
     >> >> : move all right
     >> >   : move all selected right
     >> ... same, but to left side
     >>
     >>
     >> If there's nothing like this ready-to-use, can somebody shot an idea
     >> on how to implement? Some first steps would be nice... :)
     >>
     >> In the model, would be something like:
     >> - In the left <select>, a list of "available" categories
     >> - In the right <select>, a list of "associated" categories
     >>
     >>
     >> I think on something like this:
     >>
     >> ShuttleList s = new ShuttleList("shuttle", new
     >> ShuttleModel(availableItems, selectedItems) {
     >>     public void populateItem(Item i) {
     >>         ...
     >>     }
     >> }));
     >>
     >>
     >> And then:
     >>
     >> List newSelectedItems ((ShuttleModel)
    s.getModel()).getSelectedItems();
     >>
     >>
     >> Now, 'newSelectedItems' should have objects that came from
     >> 'availableItems' and shouldn't have objects removed from
    'selectedItems'.
     >>
     >> []'s
     >>
     >> --
     >> Bruno Borges
     >> Summa Technologies Inc.
     >> www.summa-tech.com <http://www.summa-tech.com>
    <http://www.summa-tech.com>
     >> (11) 8565-7739 - (11) 3846-1622
     >
     > --
     > Philip A. Chapman
     >
     > Desktop and Web Application Development:
     > Java, .NET, PostgreSQL, MySQL, MSSQL
     > Linux, Windows 2000, Windows XP
     >







-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to