CompuServe Messages

Long file names have gone the way of the wind, I realize that the AMiga has no real limitation, the PeeCee does and we have had to deal with the lowest common denominator. I am not real sure about the States ? Picking the wrong state? I pick them by name and give the almost any length of name that I want. So i guess the answer to that is give the state a more descriptive name, or maybe I dont understand your ?. Yeah the sharp edge and other data is now FIRM no matter what you do other than mixing up the points or doing a resort. Seams, well there will always be a seam if the map is not seamless, I do think that there was a black line artifact that was wacked as a bug, but the other side of that is that if the map is not seamless you will always get some kind of seam. #: 77297 S4/Impulse 20-Mar-94 19:29:07 Mike, Regarding filenames: perhaps you misunderstood my question. I asked, "will all filename fields have a button next to them that will bring up a file requester?" Currently, Imagine offers a file requester in some cases, (e.g. when adding a new object to a scene) but in other cases (e.g. changing that object's filename after the fact) you're supposed to edit the field manually. This is poor interface design. It would be darn nice to have a file requester on _every_ filename field, in _all_ cases. Your reply, invoking PCs' 8.3-character limit, does not address the issue, since a typical filename on the PC would be C:\IMAGINE\MYPROJ.IMP\OBJECTS\MYOBJ.IOB. See? Quite a bit of typing, even if I use PC-type names. From your reply, I gather that Imagine 3.0 hasn't changed with respect to filename fields? My question about States dealt with the following situation: I created an object with many states, but several of them looked identical in shape. (This is not hard to do: add states where only attributes change, for example) When editing an existing state, I had to be very careful to remember which state I chose; if I picked the wrong name in the Update requester, I could overwrite a different state. A simple addition to the status bar, showing the object name and state, would prevent such mishaps. Finally, my question about seams on repeating altitude maps involved, of course, brushmaps which are seamless. (I'm not _that_ dumb — but you have to face mistakes like this every day on the phone, so I'm not offended) When altitude mapping a seamless image onto an object, Imagine used to show a seam where map edges met. In your reply, you wrote that this bug had been squashed. I'm glad about that, and about the other parts of my question which were addressed in your reply. Now, with the additional information in this message, can you answer my remaining questions? Thanks. Blaq!