Thread: CF 1.7 Skin Editor

perhaps you can make the border on the selection alternating colors.. on the day skins it was impossible to see where the selected area was on white portions of the skin..

Originally Posted by tj!2k4

perhaps you can make the border on the selection alternating colors.. on the day skins it was impossible to see where the selected area was on white portions of the skin..

the new version darkens the unselected area to make it more visible.

Originally Posted by justintime

Hrmmm it opens the standard skins just fine, but when I try to open mine, it says:

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WindowsApplication1.Form1.OpenFile()
at WindowsApplication1.Form1.openFileDialog1_FileOk(O bject sender, CancelEventArgs e)
at System.Windows.Forms.FileDialog.OnFileOk(CancelEventArgs e)
at System.Windows.Forms.FileDialog.DoFileOk(IntPtr lpOFN)

could you send me the skin and images etc. if possible? if not, it's okay. the code is pretty specific about some things coming from the xml file so i could try making it more flexible to fit ur skin.

I think the problem is that I had values outside of the set resolution. I did it on purpose because I did not want them to sho. For example, I had X and Y values for the drop down menu set at 2000 and 2000... COuld you add a bypass for this if not too much trouble?

Originally Posted by justintime

I think the problem is that I had values outside of the set resolution. I did it on purpose because I did not want them to sho. For example, I had X and Y values for the drop down menu set at 2000 and 2000... COuld you add a bypass for this if not too much trouble?

i should be able to do that pretty easily. will be in the new realease. will post tom. night.

Originally Posted by justintime

I think the problem is that I had values outside of the set resolution. I did it on purpose because I did not want them to sho. For example, I had X and Y values for the drop down menu set at 2000 and 2000... COuld you add a bypass for this if not too much trouble?

i looked back at the code and this shouldn't be causing the error ur recieving. it would cause a different error. this error looks as though one of ur items has more fields than nessecary. such as a button having a ROWSIZE attribute when it's not needed. would have to see the skin file to correctly diagnose.

I also cannot load my own skin for a plugin i created but can load the standard skin without an issue.

here is the error details it returns:

Code:

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

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at WindowsApplication1.Button..ctor(String[] value)
   at WindowsApplication1.Form1.OpenFile()
   at WindowsApplication1.Form1.openFileDialog1_FileOk(Object sender, CancelEventArgs e)
   at System.Windows.Forms.FileDialog.OnFileOk(CancelEventArgs e)
   at System.Windows.Forms.FileDialog.DoFileOk(IntPtr lpOFN)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
CF 1.7 Skin Editor Alpha
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/gormanly/Desktop/CF_1.7_Skin_Editor_Alpha.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

The skin is contained in the stopwatch plugin that i put up in the plugins forum. It is modified from an original version i made for 1.5 and am thinking there might be some legacy stuff left in the skin from the old version.

Originally Posted by alti

The skin is contained in the stopwatch plugin that i put up in the plugins forum. It is modified from an original version i made for 1.5 and am thinking there might be some legacy stuff left in the skin from the old version.

it would be better if the <LOADSCREEN> element were named <LOADTIMERS> to match the filename and clear a bug up. it still will not work however as i have to rewirte a bunch of code to make it more flexibile. plugin support will be availabe as soon as i have the time to do this.

i am trying to add plugin support for the app but have some questions. how would you like to open, edit, view your plugins?

A) Open the main skin file and then click a button to add any additional plugins to the existing project. Each skin file would then be stored in its respective folder.
B) Open the plugin separately and then navigate to the main_off.png file through another dialog so you can make sure the positioning of the skin is correct on the main background.
C) Open the plugin separately and just load a blank background to position the plugin to.
D) Assuming the skin file ur editing is in the centrafuse\skins directory and all plugins are either in the centrafuse\plugins and/or centraufuse\pluginsinactive folder(s), open the main skin file and all the plugins will open automiatically (not my favorite pick of the litter but i am willing to do)