Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pjcast]

I've added ability to drag and drop items form the project treeview to the scene window So, SceneEditor could have a mesh dragged, or a material dragged onto a mesh (or submesh, whatever checks the editor eants to do).

Also, because of this, I needed a way to identify material definitions in a material file. So, I hacked together a way (has to be a better method) which expands the material file in the project explorer into all defined materials

Also, as a way for a material editor to know whether a material file was selected, or a material definiton, I used the TreeNode.Name as = ResourceGroupname + " " + materialName + ".material_element"

So, to make a material editor work with that extension, just provide make material editor handle the ".material_element" extension, and you should have all the needed info (groupname, and material name, that you could also find the material file name - orgin).

[pjcast]

I've managed to stablize this. However, the method I use to get the defined materials is causing headaches in other palces. Initially, after a shutdown, and reoad of the project, the app would crash immediately. However, no it takes a few loads/unloads to see any problems. Which is more tolerable, however, not perfect at all. And, debugging is difficult with the swig layer in between the editor and Ogre.

Hence, I will be looking at the possibility of using the Managed Ogre build (MOgre) instead of the wrapper entirely. This should allow stepping into the Ogre code and see what is going on. This will also remedy a few of the other swig problems.

[pjcast]

Added ability for plug-ins to create 'named' OutputWindow's to output text to. If not specified, then the default window is used, to not break compatibility.

[pjcast]

Fixing camera movement. Still some bugs - camera is now picked which causes a crash. Not sure why yet. Also, still need to tweak camera movement.

[pjcast]

I'm going to modify the IBasicPlugin interface a bit. Firstly, I am removing the Creator propertor. Why? Well, it no longer servers a purpose. MainForm is a singleton, and so are most other things.

I will instead, add a Active property - so that plugins can be turned on/off at runtime. Turning off means that the plugin must remove all registered factories, remove any file menu hooks, and destroy any visible windows. Now, this will not happen that often, only when the user selects to disable the plugin via the plugin manager (IW soon). Once disabled, the plugin instance will be removed. So, the plugin should save any needed state information and remove any references it has placed anywhere (such as hooking into form events) - so that it can be properly GC'd.

Also, I will be adding a method to show a configuration screen (only on Active - loaded - plugins). Something like: Configure().. That will also be called via the plugin manager. This configure screen will allow the user to customize your plugin - ie. keyboard/mouse controls/ window layouts / turn on/off file loaders that the plugin registered. And anything else you need to do.

[pjcast]

Ok, changes have been added to svn:
Cleaned up IBasicPlugin.cs
Added Ability to activate/deactivate plugins.
Added PluginManager form config.
Added Configure method to IBasicPlugin so plugins can configure themselves.

Now, I fixed up all the plugins in svn. However, I did not fully implement unloading plugins in them yet, they just ignore the Active = false call

Also, I did not implement any Configuration forms yet, but the WGE one is in work.

However, Plugin Manager works good.. Setting active/unactive and storeing that information in the main config file for use on restart.

[pjcast]

Latest changes have been committed:

* Biggest is - Ogre Studio now uses Mogre instead of ODN.
* Created custom user graph control for allowing a visual editing of attenuation properties
* Working on adding some basic networking support

[mysterycoder]

Ogre Studio now has a recently opened menu. You can add as many sub-menus to it as you want. It saves the RecentlyOpened items into an xml file. The latest entries appear on top. If you open the two same things in a row, a duplicate entry will not be added, but the existing entry will be moved to the top of the list. Most importantly, when you click on an item in a RecentlOpened menu, it loads the item.  :wink:

[OvermindDL1]

You do know the Windows API has embedded support for recently opened files that internally uses the registry?  No need to emulate it, especially since you are using .NET.

[mysterycoder]

Too late.  
Plus, if pjcast ever wants to move it to linux, or mac OSX, we'll need the generic implementation.  :wink:

[pjcast]

Yeah, I do not want to rely on the windows registry. Everything done with Ogre Studio has been done with linux in mind, even if there is no linux port at the moment, I do not want to get Win32 specific in my code.. some of the libs used have win32 specific code, and will need to be ported, and I don't want to make it any harder then that

[OvermindDL1]

Your using .NET then?  I know that mono is coming along but the libraries are still lacking.

Assuming mono does finish up well someday, it would still have to emulate that same recently opened files functionality, probobly through config files of some sort, but it should still be transparent to you.

[mysterycoder]

Not if that functionality is in the Microsoft namespace, which isn't in the C# standard.

[OvermindDL1]

It's integrating into the windowing system...

[pjcast]

* Installer not yet updated, however, latest additions in work:

* Mantis bug tracker setup
* Python console/interpreter
* Bug fixes (check the mantis tracker)