Problem with

[Malte Neumann]

Hi all,

I habe a problem with the  element inside a list. If I 
add the element to my markup, the design of the list is broken in 
firefox and Chrome (windows) during designtime. Runs the markup inside 
wicket, everything works.


Here is an example of my Problem. If you open the markup in your 
browser, you see that the two lists looks different, although they 
should look the same.




ul {
list-style-type: none;
display: flex;
flex-wrap: wrap;
}

li {
border: solid red thin;
width: 25vw;
}





Item 1
Item 2
Item 3
Item 4


Item 1

Item 2
Item 3
Item 4






Does anyone have an idea on how to fix that? Otherwise I always get 
problems with my markup designer.


Regards
Malte




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Custom Component Converter not called

[Malte Neumann]

Am 07.09.2013 22:19, schrieb Sven Meier:
if you don't specify the type, a TextField will try to resolve the 
type from its model, see AbstractTextComponent#resolveType() and 
IObjectClassAwareModel.

Thanks for this hint.

During further tests after my mail, I found a situtation where the 
convertToString is called, but not the convertToObject. The initial 
situation is the same as described in the first mail. Then the model is 
updated by an ajax-call from null to a value, the output call my 
ToString-Method, but a later form submit doesn't call the 
ToObject-Method. It seems the problem occurs in 
AbstractTextComponent.resolveType. This function tries only once to 
resolve the type. In the first call the function sets type to null.


This is not my problem anymore. I can solve my special problem with the 
IObjectClassAwareModel.


Malte




>Shouldn't there be a pre-examination wheter a component converter is 
available?


Without type there can't be a converter.

Sven

On 09/07/2013 08:42 PM, Malte Neumann wrote:

Hello!

I've got a problem with a TextField and the depending 
CustomConverter. The converter of the component is not been called. 
So the default converter takes the task and fails.


In my case this problem occurs when my IModel.getObject returns null.

The problem arises in the FormComponent.convertInput method. Because 
of the null value, the typeName is null and a generic typcast is made 
and fails. Shouldn't there be a pre-examination wheter a component 
converter is available?


If I explicitly set  a type through TextField.setType my converter is 
called correctly.


Is that behaviour intended this way?

Malte

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Custom Component Converter not called

[Malte Neumann]

Hello!

I've got a problem with a TextField and the depending CustomConverter. 
The converter of the component is not been called. So the default 
converter takes the task and fails.


In my case this problem occurs when my IModel.getObject returns null.

The problem arises in the FormComponent.convertInput method. Because of 
the null value, the typeName is null and a generic typcast is made and 
fails. Shouldn't there be a pre-examination wheter a component converter 
is available?


If I explicitly set  a type through TextField.setType my converter is 
called correctly.


Is that behaviour intended this way?

Malte

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org