CompuServe Messages

Continued . . . . Thanks for converting the object, if you have downloaded my 'modified' version of it, you can tell that I had some fun with it. Having worked for Epyx, Strategic Simulations, and Spectrum HoloByte, I could no help but put in 'my two cents worth' about what I'd like to see in your application. While I haven't used your application, I would like to check out Interchange Plus, and see what features it offers. The local Amiga dealer only had an old copy, and I couldn't justify purchasing it, since it didn't offer LightWave support. Here is a wish list of things I would like to see in Interchange Plus: 1. Naming – Either drop the space or the ':' after the objects original Imagine ame. Since there is so little space in the name field of LightWave, either of the 2 characters would be adequate as a seperator, 2 chars is a was e of space. 2. Naming – I like the addition of the extended color names (ie: VERY, LIGHT, DARK, etc.), but again, it ends up being clipped by the size limit of the name field in LightWave. Though you can get the whole name when choosing 'Change Surface Name', this is kind of clunky. Maybe a better solution would be to increase the range of color names in your database, adding titles like 'OCHRE, CHARTREUSE, MAGENTA, etc.' While many users migh initially be confused by the 'artistic' names, they can just click on the color requester and find out what ochre really looks like. There would be an added benefit, as users would be trained to refer to colors by their true names, thereby serving as an educational aid for the novice artist – this could even be used as a selling point :^) 3. Naming – The HEX info is nice to have, I assume the user will get a reference card for what the initials stand for (especially since Imagine uses different surface characteristics than LightWave does). 4. Polygons – You should give the user the option of minimizing polygons on flat surfaces. This feature is found in the Data Manipulation section of Pixel-3D, and has served me quite well. I actually used this feature to optimize