by date
Codeweaver Update - Major Bug Fix, Auto Updater, and SDK
Codeweaver Update - Major Bug Fix, Auto Updater, and SDK
| Name: | Sam Bacsa | ![]() |
|---|---|---|
| Date Posted: | Feb 07, 2007 | |
| Rating: | 3.0 out of 5 | |
| Public: | YES | |
| Comments: | YES | |
| RSS Feed: | or Subscribe with . | |
| Profile Page: | View profile page for Sam Bacsa |
Blog post
(If you haven't read my previous .plan announcing CW Final, please make sure you do so you can get the full scoop on what's new in CW)
Hey all!
I've just deployed another update for CW. This one has a built-in auto-updater, so you won't have to keep downloading releases off the website.
I've fixed the issue with adding files to a project crashing the IDE. I've also enhanced the SDK support.
As per this thread on the Codeweaver forums:
You can now get the sample project for creating plugins for CW.
The sample is a clip manager. Basically what it does is it sits in the context menu of the code editor, and you can highlight stuff and click "Add to Clip Manager" for quick pasting.
The sample demonstrates the following:
- Constructing a plugin class with proper interface and attributes;
- Initialization of icon resources;
- Adding and destroying a workspace tab;
- Adding and controling a context menu item to the editor;
- Adding a context menu item in the Window -> Plugins menu;
- Adding a custom configuration page;
- Interacting with the code editor;
- Saving and loading configuration values from the global user configuration.
If you have any questions, feel free to ask.
NOTE: If you use the ConfigGetValue or ConfigSetValue, your class must pass back a valid GUID via the exposed PluginGuid property (required by the interface).
Testing/Deployment: Copy your plugin over to the \Plugins directory of the CW install folder. If it doesn't exist, create it. Make sure your DLL starts with "tdp_" (for example, "tdp_testing.dll") and it will load on startup.
I'm interested in hearing from people who are using the plugins architecture to implement things. Do let me know how you find a use for it. You can also expect updates to the plugins system with more events and hooks, down the line.
- Sam
Hey all!
I've just deployed another update for CW. This one has a built-in auto-updater, so you won't have to keep downloading releases off the website.
I've fixed the issue with adding files to a project crashing the IDE. I've also enhanced the SDK support.
As per this thread on the Codeweaver forums:
You can now get the sample project for creating plugins for CW.
The sample is a clip manager. Basically what it does is it sits in the context menu of the code editor, and you can highlight stuff and click "Add to Clip Manager" for quick pasting.
The sample demonstrates the following:
- Constructing a plugin class with proper interface and attributes;
- Initialization of icon resources;
- Adding and destroying a workspace tab;
- Adding and controling a context menu item to the editor;
- Adding a context menu item in the Window -> Plugins menu;
- Adding a custom configuration page;
- Interacting with the code editor;
- Saving and loading configuration values from the global user configuration.
If you have any questions, feel free to ask.
NOTE: If you use the ConfigGetValue or ConfigSetValue, your class must pass back a valid GUID via the exposed PluginGuid property (required by the interface).
Testing/Deployment: Copy your plugin over to the \Plugins directory of the CW install folder. If it doesn't exist, create it. Make sure your DLL starts with "tdp_" (for example, "tdp_testing.dll") and it will load on startup.
I'm interested in hearing from people who are using the plugins architecture to implement things. Do let me know how you find a use for it. You can also expect updates to the plugins system with more events and hooks, down the line.
- Sam
Recent Blog Posts
| List: | 04/04/08 - A future in the game industry - Needing your advice 03/14/08 - PGP in your Facebook 10/30/07 - Long time no speak! And a bit of personal introspection 08/27/07 - Site Back Up - Sorry! 05/09/07 - Codeweaver x64 Bug Fixed 02/07/07 - Codeweaver Update - Major Bug Fix, Auto Updater, and SDK 02/06/07 - Codeweaver Final Released! 01/27/07 - Just checking in |
|---|
Submit your own resources!| Kirakorn Chimkool (Feb 07, 2007 at 14:18 GMT) Resource Rating: 5 |
But, there is still a bug I had reported in previous post. Whenever you delete a folder from a project the IDE crash.
Edited on Feb 07, 2007 14:19 GMT
| Colossai Studios (Feb 07, 2007 at 15:17 GMT) |
| Sam Bacsa (Feb 07, 2007 at 22:06 GMT) |
This doesn't happen to me, but I'll do some research and roll out an update once I find the problem. Most likely tonight.
Take care,
Sam
| msKEN (Feb 08, 2007 at 15:15 GMT) Resource Rating: 5 |
| Rivage (Feb 08, 2007 at 16:08 GMT) |
Thanks a lot Sam !
| Andreas Kirsch (Mar 11, 2007 at 14:26 GMT) |
| Richard Wermske (May 05, 2007 at 18:56 GMT) Resource Rating: 1 |
Quote:When I do this, it recreates a new license.xml and returns the same error. Rinse and repeat.
Your license file is invalid. If you did not purchase a professional or managed license, or if you did not receive a donator's license, (in other words, if you are using the standard version of Codeweaver), please delete the 'license.xml' file from the Codeweaver directory to re-initialize the standard license.
- <!--
This license file is automatically generated. Changing
parameters will invalidate the license. Deleting this file
will cause it to be re-initialized when Codeweaver is reloaded.
To restore valid licenses, simply copy over the other license.xml
file to this location, replacing this file.
/* DEFAULT STANDARD EDITION LICENSE */
/* Features restricted: */
/* (o) Source Code Control */
/* (o) Plugins Limit is 3 */
To purchase a license, please visit www.torquedev.com.
-->
- <LicenseFile>
<LicensedToUser>Standard Edition User</LicensedToUser>
<LicensedToCompany>Codeweaver IDE</LicensedToCompany>
<LicenseLimit>Unlimited</LicenseLimit>
<LicenseSerial>CWF-134444-00UL</LicenseSerial>
- <FeatureBits>
- <!-- The sequence of this matters; do not change
-->
<Feature id="0" active="true" />
<Feature id="1" active="true" />
<Feature id="2" active="true" />
<Feature id="3" active="true" />
<Feature id="4" active="true" />
<Feature id="5" active="true" />
<Feature id="6" active="true" />
<Feature id="7" active="false" />
<Feature id="8" active="false" />
<Feature id="9" active="true" />
<Feature id="10" active="true" />
<Feature id="11" active="true" />
<Feature id="12" active="true" />
<Feature id="13" active="false" />
<Feature id="14" active="false" />
<Feature id="15" active="true" />
<Feature id="16" active="false" />
</FeatureBits>
<Expires>Never</Expires>
<Version>1.2</Version>
<VersionUpperLimit>1.3</VersionUpperLimit>
<Signature>h0laEyQn6g/aheGjS7B5G9Y0oQ8i52LyJJTXzvG/WVfVy/WacjfQng==</Signature>
</LicenseFile>
- <!-- EOF
-->
www.torquedev.com/forum/index.php
Quote:secure.netmercs.net/bugs
Table './netmercs_forum/smf_sessions' is marked as crashed and should be repaired
Quote:Any comments or hints?
There is a problem with this website's security certificate. The security certificate presented by this website was not issued by a trusted certificate authority.
Cheers,
Rich Wermske
Edited on May 05, 2007 19:07 GMT
| Sam Bacsa (May 09, 2007 at 05:35 GMT) |
Sorry for the late reply. I've been out of town for a while.
The secure bugs site uses a custom-generated certificate because I can't afford an SSL certificate just for our internal webmail and bugs reporting. I want them to be encrypted, but I don't want to buy a certificate, so you can just click on the "Continue onto this website" button in IE to move onto the bugs report form.
I fixed the forum issue this afternoon.
I also deployed an update to Codeweaver that gets past the x64 licensing error. You can run CWUpdater.exe to download the latest version.
Take care,
Sam
You must be a member and be logged in to either append comments or rate this resource.



3.0 out of 5


