hi,
after moving from wicket 6.9.1 to 6.10.0 caused all AutoCompleteTextFields
to break up in the application (no results shown). also a quick test created
from scratch with this component does not work.
does anybody experience the same?
thx
--
View this message in context:
AutoCompletePage in wicket-examples works fine here.
Sven
On 08/27/2013 10:27 AM, manuelbarzi wrote:
hi,
after moving from wicket 6.9.1 to 6.10.0 caused all AutoCompleteTextFields
to break up in the application (no results shown). also a quick test created
from scratch with this component
Wicket example works fine with AutoCompleteTextField. Can you open an
issue with your quickstart project?
does anybody experience the same?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands,
sorry, i try to be more specific. after moving to wicket 6.10.0, it fails in
two different cases:
case 1: when adding this behavior:
autoComplete.add(new AjaxFormComponentUpdatingBehavior(onKeyUp) {
@Override
protected void onUpdate(final AjaxRequestTarget target) {
Issue and quickstart please.
Sven
manuelbarzi manuelba...@gmail.com schrieb:
sorry, i try to be more specific. after moving to wicket 6.10.0, it fails in
two different cases:
case 1: when adding this behavior:
autoComplete.add(new AjaxFormComponentUpdatingBehavior(onKeyUp) {
@Override
In data lunedì 26 agosto 2013 11:28:27, francois meillet ha scritto:
have a look to
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup
/html/form/FormComponentLabel.html and
http://ci.apache.org/projects/wicket/apidocs/6.0.x/org/apache/wicket/markup
I would go a completely different route: add an AttributeModifier [1]. It
should look something like this:
Label label = new Label(label, Model.of(Text));
label.add(new AttributeModifier(class, Model.of(cssClassName)));
This is explained in more detail in the wicket-guide [2], Chapter 4.2.
In data martedì 27 agosto 2013 13:30:43, Collinson, Alasdair ha scritto:
I would go a completely different route: add an AttributeModifier [1]. It
should look something like this:
Label label = new Label(label, Model.of(Text));
label.add(new AttributeModifier(class,
It does. Here's a quick example, adapted from a quickstart:
package com.mycompany;
import org.apache.wicket.AttributeModifier;
import org.apache.wicket.request.mapper.parameter.PageParameters;
import org.apache.wicket.markup.html.basic.Label;
import org.apache.wicket.markup.html.WebPage;
import
In data martedì 27 agosto 2013 14:46:03, Collinson, Alasdair ha scritto:
It does.
I don't agree: I can't see any label tags in your markup. I don't need to
remove my label tags (and I don't want to), I need to dynamically add a
class=cssClassName to them instead.
I don't agree: I can't see any label tags in your markup. I don't need to
remove my label tags (and I don't want to), I need to dynamically add a
class=cssClassName to them instead.
Sorry, my mistake - I didn't modify the markup enough. Luckily, whether it's a
wicket:container or a label
I'm using the fantastic select2 component in my Wicket 6.7 application via
the Wicket-select2 integration package [
https://github.com/ivaynberg/wicket-select2/], version 2.2.2.
It works great on a regular page. On a page, clicking outside of the
select2 component causes the component to close.
In data martedì 27 agosto 2013 15:12:01, Collinson, Alasdair ha scritto:
So if
you change the markup in my example to
Do you see the following? -gt;label
wicket:id=version1.5-SNAPSHOT/labellt;-
It still works with the same Java-Code.
Unfortunately not, because my label tags are part of a
Hello,
I can confirm the behavior. It happens on al AutoComplete fields that are
added lazy via ajax. The mentioned error in ajax debug ERROR: Cannot find
element with id: null is produced by the script that tries to add the
autocomplete event to the element via header contribution. It seems that
Hi Jan,
autoComplete is a little delicate in the ordering of javascript event
registrations, so this might not have any effects on other components.
A quickstart will help to identify the problem.
Sven
On 08/27/2013 03:21 PM, TechDB wrote:
Hello,
I can confirm the behavior. It happens on
try that
private class FormExemple extends FormExempleModel {
public FormExemple(String myForm,
CompoundPropertyModelExempleModel model) {
super(myForm, model);
TextFieldString tf_name = new TextFieldString(name);
add(tf_name);
I added this case to JIRA with a quickstart. It is a critical bug for
my company.
https://issues.apache.org/jira/browse/WICKET-5332
Jered
On 08/27/2013 06:39 AM, Sven Meier wrote:
Hi Jan,
autoComplete is a little delicate in the ordering of javascript event
registrations, so this might
hi,
I need add some js in my AjaxSubmitLink.onSubmit(AjaxRequestTarget target,
Form? form) but it is not working. example on my onSubmit function:
@Override
protected void onSubmit (AjaxRequestTarget target, Form? form)
{
super.onSubmit(target, form);
Hi all,
I'm trying implement a RequestCycleListener which redirects the user to the
same page he initially requested but which adds a query string parameter in
certain cases. It has to be a redirect response since the parameter is
interpreted by an external system before it's forwarded to my
It appears that this fix is already working in 6.11.0-SNAPSHOT.
The fix was committed here:
https://github.com/apache/wicket/commit/bfd4649656f4f51c8d1a164cc14cb5b8dc71f89d
See https://issues.apache.org/jira/browse/WICKET-5315
I applied that change to my code and the auto complete works now.
Hello
is it possible to switch off sort, when i use OrderByBorder on DataView?
Or, better say, I'd like to change sort to 3-state behavior : asc, desc, off
Thanks in advance
Boris
-
To unsubscribe, e-mail:
What happens when you give it a null sortProperty?
~ Thank you,
Paul Bors
-Original Message-
From: Boris Brinza [mailto:boris.bri...@htsolution.sk]
Sent: Tuesday, August 27, 2013 5:48 PM
To: users@wicket.apache.org
Subject: how to switch off sort?
Hello
is it possible to switch off
Hello,
maybe i've describe problem wrong, my effort leads to 3-state
orderbyborder link.
off-asc-desc-off etc.
I've extended my data provider from SortableDataProvider and i try to
override getSort() method to achieve 3state.
It seems to work except icon shown in table header. Even i return
Try calling form.modelChanged() before you add the component to the ajax
target.
On Mon, Aug 12, 2013 at 9:37 AM, Vignesh Palanisamy
vign...@mcruncher.comwrote:
Hi,
i had a CompoundPropertyModel form.
In that form i had added RequiredTextField and a DropDownChoice.
While changing the
24 matches
Mail list logo
