(Peter Jones, updated Jan 15th 2012 by Inge) helper file can be found in your installed s4pe/Helpfiles folder, called Helpers.txt You should not design your tool so it has to use the s4pi dlls in your user's s3pe folder.
Any s4pi dlls in your bin/Release folder should be included with what you publish. This will cause it to be added to your solution's bin folder. As you need to use any s3pi dll, add it to your solution references. Unpack into folder somewhere your Visual Studio can access. A helper on the other hand can display the resource contents in a user-friendly way, prettied up, and bits hidden if they might confuse the user. The difference in concept between a helper and a wrapperĪ wrapper should be as dumb as possible and not hide or rearrange any of the data in a resource, even if we do not know what it represents, or if it is stored in a strange order. It can either be totally outside the s4pe folder like any external program, or it can live under the /Helpers folder in s4pe, inside its own subfolder along with its own dlls, with only its. A helper app can be installed in two different ways. Your tool needs to have access to the version of the dlls YOU compiled it with. This is so that if the user has an older or newer version of s4pe than the one you had when you wrote your tool, they won't end up with compatibility problems trying to use your tool. It should not rely on finding the dlls that are installed with the user's copy of s4pe. The helper should include all library dlls it relies on. The user may have to edit that if they install somewhere you did not forsee. helper text file, which you edit to call your app in the appropriate way and provide with your tool. The interface between s4pe and your app is a. But you can enhance your tool if you wish, so that it can be opened in other ways and used for other roles. s4pe) with the filename of the resource as a parameter. At minimum it must be able to be opened by being called from another application (e.g. A helper is a standalone tool that can open resources as they are exported from a package - long cryptic names and all. Simplified overview how to make a helper tool using s4pi sims4tools.sln is the solution currently in use. Buzzler - current contributions see ( ). CmarNYC - current contributions see ( ). 
IngeJones - a kind lady who doesn't want her name mentioned.snaitf - Decoding and contributions for CCOL, COBJ, trims as well as bugfixes.granthes - Several contributions pre-release and in the early stages.andrewtavera - Mesh parts and other help.ChaosMageX - Initial s4p* setup work on DATA, RIG and GEOM wrappers.The repository we forked from is not being maintained any more. Documentation on s3pi ( Sims 3 Package Interface) can be found ( ) a lot of this is still relevant. This is an open source project based on s3pi and s3pe. S4pe, based on the s4pi interface library, is an editing tool for the.
0 kommentar(er)
