gridResources.getSortModel().clear(); to reset
existing sorting - and that works.
Any ideas why it just does nothing? Am I doing something stupid here? :)
Thanks,
Rado
--
View this message in context:
http://www.nabble.com/T5%3A-disabling-column-sorting-programmatically-in-Grid-tp21546541p21546541
Em Mon, 19 Jan 2009 13:33:42 -0300, immutability devli...@bielik.org
escreveu:
So I thought of the standard way of doing this - in the
onSuccessFromFormFilter handler I do the following:
As Tapestry uses redirect-after-post by default, it does not renders the
page in the same request it
in context:
http://www.nabble.com/T5%3A-disabling-column-sorting-programmatically-in-Grid-tp21546541p21547589.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
Em Mon, 19 Jan 2009 14:27:35 -0300, immutability devli...@bielik.org
escreveu:
Thiago, thank you for a quick response, I still have a lot to learn!
You're welcome! We all stilee need a lot to learn . . .
One way to do it is to nameColumn.sortable(false) the
the method that returns the
- that
will cause an endless recursion and a stack overflow. :-)
Thanks again Thiago!
--
View this message in context:
http://www.nabble.com/T5%3A-disabling-column-sorting-programmatically-in-Grid-tp21546541p21549517.html
Sent from the Tapestry - User mailing list archive at Nabble.com
The code above should be, as found by Immutability:
public BeanModel getBeanModel() {
BeanModel model = beanModelSource.createDisplayModel(YourClass.class,
messages);
if (disableSorting) {
PropertyModel nameColumn = model.getById(name);
