| 1 |
|
2003-04-07 Jonathan Coles <[email protected]> |
| 2 |
|
|
| 3 |
|
Since we now say that the order of the groups in a classification |
| 4 |
|
matters, it makes sense to be able to manipulate that order. Most |
| 5 |
|
of the changes to Thuban/Model/classification.py are to that end. |
| 6 |
|
|
| 7 |
|
* Thuban/Model/classification.py (Classification.AppendGroup, |
| 8 |
|
Classification.InsertGroup, Classification.ReplaceGroup, |
| 9 |
|
Classification.RemoveGroup, Classification.GetGroup): Do as the |
| 10 |
|
names imply. |
| 11 |
|
(Classification.FindGroup): This was called GetGroup, but GetGroup |
| 12 |
|
takes an index, while FindGroup takes a value. |
| 13 |
|
(Classification.__deepcopy__): Copy all the groups, BUT NOT THE LAYER |
| 14 |
|
REFERENCE. Currently there is a cyclic reference between the layer |
| 15 |
|
and its classification. If the classification doesn't need to know |
| 16 |
|
its owning layer we can change this, since it may make sense to be |
| 17 |
|
able to use the same classification with different layers. |
| 18 |
|
|
| 19 |
|
* Thuban/Model/load.py: Use Classification.AppendGroup(), not AddGroup() |
| 20 |
|
|
| 21 |
|
* Thuban/UI/classgen.py: Use Classification.AppendGroup(), |
| 22 |
|
not AddGroup() |
| 23 |
|
|
| 24 |
|
* Thuban/UI/classifier.py: Now that we can depend on the order in |
| 25 |
|
a Classification and have methods to manipulate that order we don't |
| 26 |
|
need to use our own data structures in the grid. We can simply make |
| 27 |
|
the grid/table access the information they need from a copy of |
| 28 |
|
the classification object. |
| 29 |
|
(Classifier._OnCloseBtn): Event handler for when the user clicks |
| 30 |
|
'Close'. This is needed so if the user applies changes and then |
| 31 |
|
continues to change the table the user has the option of discarding |
| 32 |
|
the most recent changes and keeping what they applied. |
| 33 |
|
|
| 34 |
|
* Thuban/UI/mainwindow.py: Put "Show Legend" and "Show Session Tree" |
| 35 |
|
into the same group. |
| 36 |
|
|
| 37 |
|
* extensions/thuban/wxproj.cpp (check_version): If Thuban is compiled |
| 38 |
|
with a really old version of proj, PJ_VERSION won't even be defined. |
| 39 |
|
If it isn't defined then just compile so that the function always |
| 40 |
|
returns Py_False. |
| 41 |
|
|
| 42 |
|
* test/test_classification.py: Fix tests to use the renamed methods. |
| 43 |
|
Still need to write tests for the new methods. |
| 44 |
|
|
| 45 |
|
2003-04-04 Jonathan Coles <[email protected]> |
| 46 |
|
|
| 47 |
|
* Thuban/UI/classifier.py (Classifier.__SelectField): Move the |
| 48 |
|
call to SetSelection out of the method and before the call |
| 49 |
|
to __SelectField in __init__. This prevents a recursion of events |
| 50 |
|
when _OnFieldSelect is triggered by the user. |
| 51 |
|
|
| 52 |
2003-04-04 Jonathan Coles <[email protected]> |
2003-04-04 Jonathan Coles <[email protected]> |
| 53 |
|
|
| 54 |
* Thuban/Model/classification.py: Rename Color.None to |
* Thuban/Model/classification.py: Rename Color.None to |
Parent Directory
| 
Revision Log
| 
Patch