Thanks so much for the update. I've tested and I can now move/add objects to existing addons and my changes stick after saving.

I have one other issue with the UI and I'm not sure what I'm missing. In the following example, I've have dropped a candle onto a table and I need to position it using the UI. When I select the item, the Red, Blue and Green bars are HUGE, and I can't even see my object. The same issue occurs with the rotate bars, as well.

Is there a way to control the size of these bars? I can edit the position from within the table, but it would be so much easier to do it from the UI.

Is there a way to control the size of these bars? I can edit the position from within the table, but it would be so much easier to do it from the UI.

Not yet, sorry. I guess we need some kind of automatic scaling (depending on how far the instance is away from the camera. Feel free to post a feature request on our tracker.

I will certainly do that. Along with autoscaling, it would be nice if there were a couple of keys assigned to allow quick user tweaking from the autoscaled values. The radius, as well as the length of the bars, would be tweakable.

Are the values currently hardcoded? Can you point me toward the location in the source code were these values are currently located (or calculated)?

Glad to hear it and I know what you mean. I live in an area where it's not uncommon to lose power, occasionally for days at a time, especially during winter storms or violent thunder storms. I suppose we just take our electricity and gadgets for granted, until they're gone.

Anyway, I was thinking about submitting autoscaling as a feature request, but considering the GUI is unusable in this case, which is a typical scale one would use during editing, wouldn't it be more appropriate to flag this as a bug?

In the interim, I would like to be able to simply change the values on the fly from the prefs screen. I managed to find the code section that allows me to add it to the prefs in state.cpp and I just placed it into the General Input section.

I'm not sure how to get those values into apps/opencs/view/render/object.cpp, where they are currently declared as static constants. Can you give me a little guidance on how to proceed here? I'm an experienced coder but a bit rusty using C. I've spent the last 5 or 6 years working in Scheme and PHP, with just a little C++ here and there. I'm also very unfamiliar with the design of OpenMW project.

1. Get rid of the static constants definitions in the header and source files.
2. #include "../../model/prefs/state.hpp"
3. Replace constant definitions with state retrieval like so in the member functions: