| Table columns order hidden cache?? [message #1222068] |
Thu, 19 December 2013 10:41  |
Eclipse User |
|
|
|
Hi,
I'm doing the MiniCRM (great) tutorial, and have come to an odd situation.
While creating the Person page I've created the columns in the wrong order (person_nr, first_name, last_name). After running with the suggested query it obviouslly was showing the last name value in first name column and vice-versa.
So to fix this (and also try the Scout limits  ) I've drag-and-dropped the last_name column to the correct order in the Scout Explorer view. This has correctly fixed the code order and annotations:
@Order(20.0)
public class LastNameColumn extends AbstractStringColumn {
...
@Override
protected int getConfiguredWidth() {
return 200;
}
}
@Order(30.0)
public class FirstNameColumn extends AbstractStringColumn {
...
}
So after this change, I've also setted the width for both name columns.
For me the logical result for this would be to have a table with first column having the last_name, and the second column having the first_name, and both columns having 200 as width.
For my big surprise the clients (at least SWT & RAP) presented something different:
1. kept the original/erroneous column orders (first_name, last_name).
2. Now the data was correctly loaded with the suggested query (as expected)
3. First Name now had a 200 width, but Last Name remained with the initial width.
To be sure I've seen the advanced properties and seen that ViewOrder was still -1, so there wasn't no apparent reason for not updating the columns order.
Just for a try I've cleaned all my projects, and deleted the runtime information that was created with the project. Still the columns were unsorted.
In this "plays" I've seen that columns widths are persisted in between executions, even if runtime information is deleted. But if I configure in a execution the columns order, this configuration isn't persisted for the following execution.
Just for a relief I've restarted eclipse to see if some in-memory thing was going on.
So where is the "black magic" that is generating this table???
My humble guess there must be some "cache" holding this values but isn't in the obvious places (maybe in workspace metadata or some plugins data??).
Also what other mysterious problems like this can we expect in this changes?
Regards
João
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04486 seconds
Home