CompuServe Messages

Hi Greg, Welcome to the wonderful world of "That ain't quite what they say". I've posted those same questions a couple of months ago and never got any real explanation either. To your first question: No. The frame info you get is for the entire sequence. The information is redundant. You have to ask the user the number of frames the process will work for and the starting frame. To your second question: All stuff related to field mode is undocumented. Your best bet is to download the stuff Gary (Yost) uploaded here. There you will find example source of IXP's making use of the new structure items handling field mode. To your third question: String gadgets are pretty sensitive to the info you provide. This is a nightmare. The definition of the structure is backwards (where you define the length and how much you want displayed). The limits (as to how long they can be) appear to be rather random. My best luck was trial and error untill I managed to get a set of string gadgets that wouldn't "reboot" the system. It's also very importand to understand how to send back to 3DS the variable length. This is done in ClientVarSize(). Make sure the string is rounded of to a 4 bytes boundary (you have it as 13 bytes long). In your code, I noticed a couple of strange things. I have to say I haven't had much time to study it in detail but here is what I found: In your State structure initialization, you set the colors to float values. The elements (r,g,and b) are unsigned char. You also define "length" to be of type "long" but fail to tell 3DS about it in ClientVarSize(). Remember that a long here is 64 bits long. This is far as I go. Good luck.