the right thing to do would be to provide a patch back to the community... -igor
On Wed, Apr 22, 2009 at 7:52 AM, Eyal Golan <[email protected]> wrote: > With pleasure. > > 1. I overridden Palette.java and Palette.html > In Palette.html I added the line below (with the span). > In Palette.java all we did is override renderHead (see below) > 2. We created a new palette.js and added the script file as below. > > Hope that helps. > > Eyal Golan > [email protected] > > Visit: http://jvdrums.sourceforge.net/ > LinkedIn: http://www.linkedin.com/in/egolan74 > > P Save a tree. Please don't print this e-mail unless it's really necessary > > > On Wed, Apr 22, 2009 at 5:34 PM, Carlo Camerino <[email protected]>wrote: > >> I think we are also expericning this problem same as yours >> If you will allow, can I have a copy of your fix for this one? >> what files did you modify? >> Thanks >> >> Carlo >> >> 2009/4/22 Eyal Golan <[email protected]> >> >> > I fixed the annoying thing by overriding the html panel of the palette >> > (which I did previously for other purposes) and adding an element (1484 >> is >> > our bugzilla issue number): >> > <!-- Do not remove ie7bug-1484. customepalette.js uses this element --> >> > <span id="ie7bug-1484" style="display: none;"></span> >> > >> > Also: >> > /** >> > * Renders header contributions >> > * >> > * @param response >> > */ >> > �...@override >> > public void renderHead(IHeaderResponse response) { >> > super.renderHead(response); >> > response.renderJavascriptReference(new >> > ResourceReference(CustomPalette.class, "customepalette.js")); >> > } >> > >> > and finally: >> > Wicket.Palette.moveUp=function(choicesId, selectionId, recorderId) { >> > var selection=Wicket.Palette.$(selectionId); >> > >> > if (Wicket.Palette.moveUpHelper(selection)) { >> > document.getElementById('ie7bug-1484').innerHTML = ''; >> > var recorder=Wicket.Palette.$(recorderId); >> > Wicket.Palette.updateRecorder(selection, recorder); >> > } else { >> > document.getElementById('ie7bug-1484').innerHTML = ''; >> > } >> > } >> > >> > I really don't like these kinds of hacks, but what can I say? IE7 >> wouldn't >> > let me any other option. >> > >> > Eyal Golan >> > [email protected] >> > >> > Visit: http://jvdrums.sourceforge.net/ >> > LinkedIn: http://www.linkedin.com/in/egolan74 >> > >> > P Save a tree. Please don't print this e-mail unless it's really >> necessary >> > >> > >> > On Wed, Apr 22, 2009 at 12:13 PM, Eyal Golan <[email protected]> wrote: >> > >> > > We have a very strange behavior in palette and IE7. >> > > We use Wicket 1.3.4 . >> > > >> > > The situation is: >> > > when pressing the UP button, the selected element goes up in each >> click. >> > > That's OK. >> > > The problem occurs when this element is in the second row. >> > > When pressing UP, it won't go to the first (upper) row. Only when we >> move >> > > the mouse to the area of the selected elements it goes up. >> > > >> > > In FF it doesn't happen. >> > > in IE6 it doesn't happen as well. >> > > >> > > I looked in the mailing list and couldn't see something about it. >> > > >> > > Was it fixed in 1.3.5 ? >> > > >> > > Thanks >> > > >> > > >> > > Eyal Golan >> > > [email protected] >> > > >> > > Visit: http://jvdrums.sourceforge.net/ >> > > LinkedIn: http://www.linkedin.com/in/egolan74 >> > > >> > > P Save a tree. Please don't print this e-mail unless it's really >> > necessary >> > > >> > >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
