Tomahawk Input Calendar is showing in the wrong position

2011-03-17 Thread emerson
We changed the template of the page, and afterwards the calendar popup started to appear away from the button. The component configuration is: t:inputCalendar value=#{ConsultaDiarioForm.dataInicio} renderPopupButtonAsImage=true renderAsPopup=true popupWeekString=Semana size=10

Re: Tomahawk Input Calendar is showing in the wrong position

2011-03-17 Thread Leonardo Uribe
Hi That is something new. I have never seen that before. Maybe some css configuration affects the div or the calendar, so maybe you need to create a custom theme for the calendar so you can override the default values where the popup appear. The properties to do that are styleLocation,

Re: Tomahawk Input Calendar is showing in the wrong position

2011-03-17 Thread emerson
What would be the original CSS on regards to location? Would it possible to just override that positioning without loosing the rest of the CSS? thanks emerson On 17 March 2011 15:40, Leonardo Uribe lu4...@gmail.com wrote: Hi That is something new. I have never seen that before. Maybe some css

Re: Tomahawk Input Calendar is showing in the wrong position

2011-03-17 Thread Leonardo Uribe
Hi To locate the default files it uses tomahawk AddResource api. In tomahawk for JSF 2.0 it uses the new ResourceHandler that is part of the standard api. In the first case look on tomahawk jar on org/apache/myfaces/custom/calendar/resource/ path. You'll see two themes (DB and WH).

Re: Tomahawk Input Calendar is showing in the wrong position

2011-03-17 Thread emerson
Thanks Leonardo! On 17 March 2011 16:28, Leonardo Uribe lu4...@gmail.com wrote: Hi To locate the default files it uses tomahawk AddResource api. In tomahawk for JSF 2.0 it uses the new ResourceHandler that is part of the standard api. In the first case look on tomahawk jar on

Re: Tomahawk Input Calendar is showing in the wrong position

2011-03-17 Thread Werner Punz
Hi Leo I am not entirely sure but as far as I can remember the input calendar basically does some offset calculation to determine the position, as far as I recall this is due to the fact that it needs an outer form to submit its values. Now given all the browser quirks in the past this offset