Brode

Are you getting any error messages when you try to open one? Which mods are you looking at?

the ui ive tried are http://www.lotrointerface.com/downlo...ckFadeWIP.html
and it throws up this message

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at LOTRO_Skin_Editor.SkinDefinition.load(ToolStripLab el sLabel, ToolStripProgressBar bar)
at LOTRO_Skin_Editor.Form1.openToolStripButton_Click( Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Obje ct key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(Eve ntArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(Eve ntArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(M ouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventIntera ctive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(Event Args e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEven tArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(M ouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Mes sage& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
LOTRO Skin Editor
Assembly Version: 0.19.0.0
Win32 Version: 0.19.0.0
CodeBase: file:///C:/Users/Clink/Desktop/LOTRO%20Skin%20Editor/LOTRO%20Skin%20Editor.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.232 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SlimDX
Assembly Version: 4.0.11.43
Win32 Version:
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/SlimDX/v4.0_4.0.11.43__b1b0c32fd1ffe4f9/SlimDX.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Design
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Design/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Design.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Drawing.Design
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing.Design/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

D.H1cks

Thanks.

This was all I really needed to see, and the name of the skin you are trying, which also fails for me. Now to find out why.....


EDIT: okay, to get the skins to load, you will need to edit the SkinDefinition.xml file for each one manually to fix a minor problem. Search each one for the following entry:

change aFileName to just FileName.

Now I need to fix my app to not throw an exception while handling another

Brode

that worked! Thanks bunches

joshmiller83

When loading a New Skin or an existing Skin all I see is everything in Red Squares... What is going on?

D.H1cks

Red squares means that the editor did not find any graphics to display those particular elements.

I do not include any default graphics with the editors.

You can click on the Hide Missing Art checkbox on the right hand side to stop showing the red squares also.

joshmiller83

Ah... So I need to find out where to download the Default Graphics, huh? Thanks!

zanttux

Getting better and better with every release. Keep up the good job.

Thorinn

Hey there, i download the tool and its working fine but.. how can i change the vitals colour, add images?..

D.H1cks

Unfortunately there are a number of elements that we do not have access to for changing the image. The vitals colour is one of those, so is the XP colour in the main toolbar.

Mynameisme

Hi,

I downloaded the tool and it works fine, but I'm wondering - why won't the Daimon UI show up? I wanted to be able to change the looks of the vitals for the certain ones... but it's not being detected. Any ideas?

D.H1cks

Yup, I have an idea. It doesn't show up because I only look one folder deep in the Skins directory for SkinDef files. In order to use DamonUI, you will need to open the file by selecting the file manally. Goto File->Open....

I will work on adding deeper searching in a future version.

Mynameisme

Thanks ^^

This is my first time really doing something like this, so could you help and perhaps explain a little on how to change the vitals of the Mini DaimonUI4 version with the normal DaimonUI4 version

D.H1cks

To be honest, my app would not be very good at doing this type of thing very quickly. You would basically have to copy all the properties for the vitals from the skin you like but don't want to use, and put them into the skin you want to use. Doing this one at a time in the editor would be a pain. Though it does give me an idea for another future feature.

The better bet would be to open the SkinDef file with the Vitals you want to use, find the block of XML for the vitals, and copy them into the SkinDef of the skin you want to use, making sure to replace the same block. You would also have to find all the image mappings and make sure they are copied as well.

PM me if you need more specific details.

Hyperactive Child

everything works killer as always, just wondering why you have the elements load invisible now. You made me actually go read to find out why i couldn't see anything!

D.H1cks

Starting it up and having it show approximately 90 panels at once was not so fun. It ran fine, but is just a mess. I thought people would prefer to only show the few panels they are actually working on rather than disable a large number.