 |
This is a UI problem -- you are editing only a single key ("model"), so it would be incorrect for the Model Selector to change another key ("skin") outside of the current PropertyEditor. The ModelSelector should have an option whether to display skins or not, and if it is invoked from the EntityInspector the skins should not be shown. |
|
|
Investigated how to hide the skins. Not adding them during construction if a parameter is set does not work because the dialog is persistent, and will not be constructed more than once. The most appropriate tool appears to be the GtkTreeModelFilter, which wraps a GtkTreeModel and provides filtering capabilities, but unfortunately (1) this seems to break sorting, because the GtkTreeView expects the underlying GtkTreeModel to implement the GtkTreeSortable interface (which GtkTreeStore does, but GtkTreeModelFilter doesn't), and (2) it seems impossible to reset the GtkTreeModelFilterVisibleFunc once it has been set, meaning that this cannot be used to switch filtering on and off. More investigation needed. |
 |
How about adding a submenu to the orthoview's context menu? Like this: + |-Create Entity ---------------- |-Model... >>> Create... | >>> Change Model... | >>> Change Skin... | >>> Surround with Monsterclip | >>> Surround with Playerclip ---------------- .... |
|
|
That would be reasonable from a usability point of view, but the issue with skins being displayed in the "Select model" dialog for the ModelPropertyEditor would still need to be solved somehow. It might be easiest just to create two GtkTreeStore's in parallel and switch the GtkTreeView between the two models depending on whether skins should be displayed or not. |
|
|
I think the solution of having two separate treemodels in the background is a pragmatic one. Do you mind if I look into this? |
|
|
Fixed by maintaining two separate treemodels. |
- Anonymous
