#ogitors

[fdastero-blog]

hax it for now

So I decide to workaround the issue. I don't really want to implement a custom terraintoolwidget. I rather get the feature working first then make it look right, so I will still be reusing the widget. The workaround is a single line modification in qtOgitors mainwindow.cpp, where the terraintoolwidget is added to the default terrain editor factories. I just grab my own terrain editor factory and attach the widget to it. It's that simple. In the future I may write a patch and let plugins have the ability to register themselves and have it so in mainwindow.cpp we iterate all the registered factories and attach the custom widget to it. Although I have to ask the forums to see if this is indeed necessary.

[fdastero-blog]

May have to implement own widget. Cannot use default widget

In Ogitors there is a derived class of QWidget called TerrainToolsWidget. This widget basically provides the GUI functionality for terrain editing. My original plan was to implement the ITerrain interface and somehow use this TerrainToolsWidget. I was able to make small headway toward this effort because I discovered that if any sub-class of BaseEditor implements IsTerrainType and returns true, then it is considered an editor capable of doing terrain editing. So I thought, that means TerrainToolsWidget will be attached to it.

Nope. I noticed that in qtOgitors, TerrainToolsWidget is manually attached to TerrainEditor by getting the default built-in terrain editors by invoking GetEditorFactory and setting the widget on it. Since qtOgitors is a standalone executable, it's impossible to get this widget from qtOgitors. I haven't found a mechanism to attach TerrainToolsWidget to my custom ediotr. Thus I can't use this widget. This means I have to now implement my own TerrainToolsWidget!

Gonna ask on the forum and call it a day.