Didn't work for me though
Tested this when I saw this at BI Forums but forgot to report about this...
When I opened a script from a .pbo, edited it and tried to save it back in the .pbo, .NET Framework gives me this message:
Unhandled exeption has occurred in your application. blah blah.
Could not find file 'E:\OFP Editing\3rd Party\OFPScriptEditor\func_test\int.sqs'.
And the detailed window shows this:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'E:\OFP Editing\3rd Party\OFPScriptEditor\func_test\int.sqs'.
File name: 'E:\OFP Editing\3rd Party\OFPScriptEditor\func_test\int.sqs'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at Editor.Form1.saveFileDialog_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
----------------------------------------
Editor
Assembly Version: 1.0.2342.24194
Win32 Version:
CodeBase: file:///E:/OFP%20Editing/3rd%20Party/OFPScriptEditor/Editor.exe
----------------------------------------
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd/msvcm80.dll
----------------------------------------
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.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.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.
I don't know if something is hinky with my OS, for example none of the Mikero's tools with GUI that are written in VB work for me..
Seems to be a handy tool though, but I doubt I would be changing into this...
Having used Chris' OFP Script Editor for years and again years of updating scripts in pbos by editing a script and then updating the whole pbo with some bpoing tool has become so automatic it slows down my work if I have to start learning new 'tricks'... Too old for that I guess
Anyway, if this had the CHOPSE functionality like project files tree and customisable (is that even a word?) syntax highlighting colors this would be a good 'competitor' for it..
I tried it and it's selfexplaining.
That doesn't change the fact that what Planck said is valid..