A Dissabte, 1 d'agost de 2009, Ferdinand @ ChriCar va escriure:
> sorry to say it's really a showstopper
>
> when it comes to sort functional fields by id -> chaotic order ..user
> must think it's borken ..:-((
Right. Just commited r907. Given that this had to be carried out in the server
I added a new service in the 'koo' module. So if you have the module installed
you'll be able to sort by many2one fields. Drawbacks:
- Just like in other cases, if many2one "name" field is a function it won't be
sorted. You'll need store=True for that.
- Translatable fields are sorted by the default (english) language. OpenObject
doesn't support this either so I think a bug or blueprint should be reported
to the project.
If 'koo' module is not installed behaviour is exactly the same as it was. If
users don't like it, they can use GTK-like behaviour by loading only 80 rows.
A Dissabte, 1 d'agost de 2009, Ferdinand @ ChriCar va escriure:
> sorry to say it's really a showstopper
>
> when it comes to sort functional fields by id -> chaotic order ..user
> must think it's borken ..:-((
Right. Just commited r907. Given that this had to be carried out in the server
I added a new service in the 'koo' module. So if you have the module installed
you'll be able to sort by many2one fields. Drawbacks:
- Just like in other cases, if many2one "name" field is a function it won't be
sorted. You'll need store=True for that.
- Translatable fields are sorted by the default (english) language. OpenObject
doesn't support this either so I think a bug or blueprint should be reported
to the project.
If 'koo' module is not installed behaviour is exactly the same as it was. If
users don't like it, they can use GTK-like behaviour by loading only 80 rows.
-- www.NaN- tic.com
Albert Cervera i Areny
http://
Mòbil: +34 669 40 40 18