Print

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

[Tecknojock]

The new object button doesn't seem to be creating objects. It throws the prompt, but after I hit create, the object never shows up.

EDIT: Maybe I'm doing something wrong. I tried it in Beta 1, 1.1, 1.2, 2, and 3 and in none of them could I create a new object, or at least none that I could find. 

Also, when I try to import from a raw file without a graphics folder, the program crashes, but placing an empty graphics folder in the raw resolves this.

This is the exception thrown when you try and import when a graphics folder is not located in the raw directory:

Code: [Select]

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

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'F:\PortableApps\Dwarf Fortress\raw\graphics\'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileSystemEnumerableIterator`1.CommonInit()
   at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler)
   at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)
   at System.IO.Directory.InternalGetFiles(String path, String searchPattern, SearchOption searchOption)
   at RawExplorer.RawLibrary.parseDirectory(String directory) in C:\Users\bradley.uffner\Documents\Visual Studio 2010\Projects\Raw Explorer\Trunk\RawExplorer\RawExplorer\RawLibrary.vb:line 104
   at RawExplorer.RawLibrary.parseRawDirectory(String directory) in C:\Users\bradley.uffner\Documents\Visual Studio 2010\Projects\Raw Explorer\Trunk\RawExplorer\RawExplorer\RawLibrary.vb:line 99
   at RawExplorer.RawExplorerForm.mnuLoadRaws_Click(Object sender, ItemClickEventArgs e) in C:\Users\bradley.uffner\Documents\Visual Studio 2010\Projects\Raw Explorer\Trunk\RawExplorer\RawExplorer\RawExplorerForm.vb:line 129
   at DevExpress.XtraBars.BarItem.OnClick(BarItemLink link)
   at DevExpress.XtraBars.BarItemLink.OnLinkClick()
   at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(BarLinkAction action, Object actionArgs)
   at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(BarItemLink link)
   at DevExpress.XtraBars.Controls.CustomLinksControl.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at DevExpress.XtraBars.Controls.CustomControl.WndProc(Message& msg)
   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/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
RawExplorer
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/RawExplorer.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.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
----------------------------------------
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.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.Runtime.Remoting
    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.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
Common
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/Common.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
----------------------------------------
DevExpress.Utils.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.Utils.v11.2.DLL
----------------------------------------
DevExpress.Data.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.Data.v11.2.DLL
----------------------------------------
DevExpress.XtraTreeList.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraTreeList.v11.2.DLL
----------------------------------------
DevExpress.XtraEditors.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraEditors.v11.2.DLL
----------------------------------------
DevExpress.XtraGrid.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraGrid.v11.2.DLL
----------------------------------------
DevExpress.XtraBars.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraBars.v11.2.DLL
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
DevExpress.XtraLayout.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraLayout.v11.2.DLL
----------------------------------------
WindowsBase
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.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.


[BradUffner]

The new object button doesn't seem to be creating objects. It throws the prompt, but after I hit create, the object never shows up.

EDIT: Maybe I'm doing something wrong. I tried it in Beta 1, 1.1, 1.2, 2, and 3 and in none of them could I create a new object, or at least none that I could find. 

Also, when I try to import from a raw file without a graphics folder, the program crashes, but placing an empty graphics folder in the raw resolves this.

This is the exception thrown when you try and import when a graphics folder is not located in the raw directory:

Code: [Select]

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

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'F:\PortableApps\Dwarf Fortress\raw\graphics\'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileSystemEnumerableIterator`1.CommonInit()
   at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler)
   at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)
   at System.IO.Directory.InternalGetFiles(String path, String searchPattern, SearchOption searchOption)
   at RawExplorer.RawLibrary.parseDirectory(String directory) in C:\Users\bradley.uffner\Documents\Visual Studio 2010\Projects\Raw Explorer\Trunk\RawExplorer\RawExplorer\RawLibrary.vb:line 104
   at RawExplorer.RawLibrary.parseRawDirectory(String directory) in C:\Users\bradley.uffner\Documents\Visual Studio 2010\Projects\Raw Explorer\Trunk\RawExplorer\RawExplorer\RawLibrary.vb:line 99
   at RawExplorer.RawExplorerForm.mnuLoadRaws_Click(Object sender, ItemClickEventArgs e) in C:\Users\bradley.uffner\Documents\Visual Studio 2010\Projects\Raw Explorer\Trunk\RawExplorer\RawExplorer\RawExplorerForm.vb:line 129
   at DevExpress.XtraBars.BarItem.OnClick(BarItemLink link)
   at DevExpress.XtraBars.BarItemLink.OnLinkClick()
   at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(BarLinkAction action, Object actionArgs)
   at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(BarItemLink link)
   at DevExpress.XtraBars.Controls.CustomLinksControl.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at DevExpress.XtraBars.Controls.CustomControl.WndProc(Message& msg)
   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/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
RawExplorer
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/RawExplorer.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.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
----------------------------------------
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.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.Runtime.Remoting
    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.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
Common
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/Common.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
----------------------------------------
DevExpress.Utils.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.Utils.v11.2.DLL
----------------------------------------
DevExpress.Data.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.Data.v11.2.DLL
----------------------------------------
DevExpress.XtraTreeList.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraTreeList.v11.2.DLL
----------------------------------------
DevExpress.XtraEditors.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraEditors.v11.2.DLL
----------------------------------------
DevExpress.XtraGrid.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraGrid.v11.2.DLL
----------------------------------------
DevExpress.XtraBars.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraBars.v11.2.DLL
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
DevExpress.XtraLayout.v11.2
    Assembly Version: 11.2.10.0
    Win32 Version: 11.2.10.0
    CodeBase: file:///F:/PortableApps/Dwarf%20Fortress/LNP/Utilities/2-Advanced/Raw%20Explorer/DevExpress.XtraLayout.v11.2.DLL
----------------------------------------
WindowsBase
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.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.


It's probably related to the changes that I made that allow you to add new objects via the clip board.  I'll  have both of these fixed asap.

[BradUffner]

I'ts probably related to the changes that I made that allow you to add new objects via the clip board.  I'll  have both of these fixed asap.

The ability to create new object is actually fairly

Or..., it could be related to the fact that I left the code blank in that sub <facePalm/>  At least it's an easy fix.

[BradUffner]

Beta 3.1 has been released in the first post.
It fixes both bugs listed by Tecknojock.

[Tecknojock]

Thanks, works great now.

[i2amroy]

Recently I accidentally entered an integer into a spot that shouldn't have accepted that integer and the program accepted it without even popping up a warning message. Currently setting limits on integers appears to have no effect at all in program for what it allows you to put into the spot. This might just be a feature that you haven't got around to yet, but I had been fairly sure that you had added that in already so I'm reporting it.

To be more specific [UNDERGROUND_DEPTH:X:X] should only accept integers from 0 to 5 and even though it states that it only accepts those it will actually let you plug any integer you want into the arguments without even popping up a warning message.

Edit: One more thing. Currently you have all of the [BODYGLOSS:XX] entries all piled up as tokens on the UPPERBODY_PINCERS entry. In truth these are actually entirely different entries, similar to [BODY: entries, not tokens. They just only have one argument each instead of having tokens on each one. This seems to only occur if I try to start the definition of the new token by clicking on the "type" field instead of typing the name.

Edit2: Third thing. Whenever I define a new argument and chose from the list of types it always selects "integer" regardless of what I click on. Once it has chosen integer it works fine and changes to what I click on, but the first time it always selects integer. This could be a side effect of your code that automatically sets the type of any new arguments to "integer".

[Jeoshua]

If my submission to the token library was accepted that UNDERGROUND_DEPTH thing may be my fault, due to not really understanding how to set those kind of things. 

[i2amroy]

If my submission to the token library was accepted that UNDERGROUND_DEPTH thing may be my fault, due to not really understanding how to set those kind of things. 

No I've checked it and it's formatted right. The problem seems to be that the program isn't stopping you from inputting integers that are beyond the accepted ranges. I've checked a couple of other areas where an integer should be limited and they suffer from the same problem.

Also one more thing, the [SYN_INGESTED] token currently has no "allowed on" or "usage" areas. Whenever I try to add a usage area I then get the message "Unhandled exception has occurred in this application". Clicking on the "details" button does absolutely nothing different from clicking on "Continue". The other [SYNDROME_X] tokens appear to function fine though.

Edit: Another thing! Currently there are a few values which can technically accept negative values (Namely the [MATERIAL_VALUE:X] token). I was just wondering if your "integer" argument would naturally allow for those or no (considering that the limits were fixed that is).

Edit2: And another! I seem to have some problem at times getting the changed definition to send to the website. As far as I can tell if you just change the arguments on a thing that already has at least one argument defined then it doesn't send to the website when you click "save". If the token doesn't have any arguments defined or if you change the description then it sends, but if it has some arguments defined and you only change the arguments it doesn't send. The same thing also appears to happen if I only edit the "allowed on" field without changing the description field.

Edit3: One more! Anytime that I create an ALL:ALL usage token it changes the current displayed information for the token to unknown and blanks out all of the fields in the editor until I redownload the token definitions (after it has been applied).

Final Edit: I just noticed that if I right-click anywhere in the definition editor that isn't in a field then I have the "Customize Layout" option. Selecting this then opens up a menu that looks a little complex for the average user to be intended to open and looks more like something you would be using to edit the layout so I wasn't sure if you wanted it to be able to be accessed.

Sorry for dropping all of these various bugs/questions into your lap overnight! I guess that's what I get for throwing up 200-300 more token definitions in the middle of the night when nobody else is online. Anyways, I'm out for the night!

[BradUffner]

If my submission to the token library was accepted that UNDERGROUND_DEPTH thing may be my fault, due to not really understanding how to set those kind of things. 

No I've checked it and it's formatted right. The problem seems to be that the program isn't stopping you from inputting integers that are beyond the accepted ranges. I've checked a couple of other areas where an integer should be limited and they suffer from the same problem.

Also one more thing, the [SYN_INGESTED] token currently has no "allowed on" or "usage" areas. Whenever I try to add a usage area I then get the message "Unhandled exception has occurred in this application". Clicking on the "details" button does absolutely nothing different from clicking on "Continue". The other [SYNDROME_X] tokens appear to function fine though.

Edit: Another thing! Currently there are a few values which can technically accept negative values (Namely the [MATERIAL_VALUE:X] token). I was just wondering if your "integer" argument would naturally allow for those or no (considering that the limits were fixed that is).

Edit2: And another! I seem to have some problem at times getting the changed definition to send to the website. As far as I can tell if you just change the arguments on a thing that already has at least one argument defined then it doesn't send to the website when you click "save". If the token doesn't have any arguments defined or if you change the description then it sends, but if it has some arguments defined and you only change the arguments it doesn't send. The same thing also appears to happen if I only edit the "allowed on" field without changing the description field.

Edit3: One more! Anytime that I create an ALL:ALL usage token it changes the current displayed information for the token to unknown and blanks out all of the fields in the editor until I redownload the token definitions (after it has been applied).

Final Edit: I just noticed that if I right-click anywhere in the definition editor that isn't in a field then I have the "Customize Layout" option. Selecting this then opens up a menu that looks a little complex for the average user to be intended to open and looks more like something you would be using to edit the layout so I wasn't sure if you wanted it to be able to be accessed.

Sorry for dropping all of these various bugs/questions into your lap overnight! I guess that's what I get for throwing up 200-300 more token definitions in the middle of the night when nobody else is online. Anyways, I'm out for the night!

Thanks for the bug reports!  I'll try to get fixes out for the most important ones first.

Apparently the Argument Grid decided to just stop validating input entirely at some point.  It just let me put in the value "cat" on something that is an integer only.  I'm not sure when that broken. UPDATE Found and fixed the problem for next version.

Far the items that were just questions:
It will accept negative numbers just fine, but you have to change the typeData to allow it.  If the typeData is blank it will only accept posative values. To accept negative numbers use something like "-1000000 1000000".  Thinking about this now I see that I need to add a better way (so you don't need to know the full range).  What do you think of setting typeData to "+-" to allow the full range of positive and negative numbers?

[BradUffner]

Beta 3.2 is now up!
This update fixes all the bugs reported by Jeoshua and i2amroy.

[BradUffner]

Recently I accidentally entered an integer into a spot that shouldn't have accepted that integer and the program accepted it without even popping up a warning message. Currently setting limits on integers appears to have no effect at all in program for what it allows you to put into the spot. This might just be a feature that you haven't got around to yet, but I had been fairly sure that you had added that in already so I'm reporting it.

To be more specific [UNDERGROUND_DEPTH:X:X] should only accept integers from 0 to 5 and even though it states that it only accepts those it will actually let you plug any integer you want into the arguments without even popping up a warning message.

Edit: One more thing. Currently you have all of the [BODYGLOSS:XX] entries all piled up as tokens on the UPPERBODY_PINCERS entry. In truth these are actually entirely different entries, similar to [BODY: entries, not tokens. They just only have one argument each instead of having tokens on each one. This seems to only occur if I try to start the definition of the new token by clicking on the "type" field instead of typing the name.

Edit2: Third thing. Whenever I define a new argument and chose from the list of types it always selects "integer" regardless of what I click on. Once it has chosen integer it works fine and changes to what I click on, but the first time it always selects integer. This could be a side effect of your code that automatically sets the type of any new arguments to "integer".

Oops, I missed this comment when I was going through the new bugs.

The thing you mentioned with underground_depth should be fixed with beta 3.2.

I'm not sure I entirely understand BODYGLOSS.  I've read the wiki and looked at how it's used in the raws, but it's not clicking for me.  I know it's not handled correctly at the moment, maybe I should have it completely skip it until I know how to properly handle it.  Could you (or someone else) explain in more detail how BODYGLOSS is supposed to work?  If you have any ideas on how raw explorer should present it in the UI I'd be open to hearing them. update - Actually, on reading the wiki page again more carefully, I think I understand it now.

The argument type resetting back to integer has been fixed for the next version. I don't think it's worth doing a new point release just for that.

[Jeoshua]

Suggestion for once you've gotten through the token processing stage:

Creatures will grab the graphics tile from the raws and display it on the "folder" selection side.  If there isn't a graphics tile, they correctly display the creature's ascii tile.

- Creatures with an ALT_TILE should blink between the two, as they do in-game
- Plants should display their tiles in the same way as creatures
- Items should display their tiles
- Inorganics should display their tiles And/Or their colors (if no tile is given)

[BradUffner]

I've got another question for the modders.

I've almost got the "item" argument type complete, and the "material" type specific to reactions also. But in the process I found a discrepancy between the Raws and the Wiki.  This page http://dwarffortresswiki.org/index.php/DF2012:Item_token says that items without a subtype should use "NONE" as the subtype. However, reactions from the raw files show it using "NO_SUBTYPE".  Other places where the "item" type is used actually use "NONE".  Is there a functional different between NONE and NO_SUBTYPE?  Is NO_SUBTYPE exclusive to reactions, or could it be used anywhere with NONE and NO_SUBTYPE being equivalent?

[i2amroy]

As far as I know NO_SUBTYPE and NONE are functionally equivalent and can be used interchangeably. I always tend to just use NONE because it is shorter. If I remember correctly then back in 40d NO_SUBTYPE was what you used in the raws and NONE was what was used for embark profiles, but with DF 2010 Toady combined them so that both NONE and NO_SUBTYPE could be used in the raws themselves. As a result the older reactions (such as the smelter ones) use NO_SUBTYPE since they were created back when that was the only option. The newer ones all use NONE though since they were created after that option was available.

[BradUffner]

Thanks for the info.  I'll make sure both options are available.