|
2005-05-23 00:24
|
|
|
2005-05-23 00:24
|
tmcompare.jpg (32,957 bytes) |
|
|
I've already been sent a fix for this and it will go in later tonight. If it isn't fixed in the next available build then reopen this bug. |
|
|
This is probably my fault. Which build does this first appear in? |
|
|
drat!. The day i release a test build, another bug is fixed :) |
|
|
It is your fault Goober. ;) It's because of the way Training_buf and Training_lines work together. When a change is made to Training_lines it makes that same change to Training_buf. That's why Training_text was there, to have a clean copy to reset the message. When it goes through the split lines it will put NULL at the end of the line. This ends up in Training _buf as well which is why it ends up showing only one line. It does show all of the lines the first frame but doesn't at any time later. The basic fix I have is to spilt_str just the once in message_training_setup() but I really don't know if that breaks any variable replacement which is why I haven't put it in CVS yet. Simply going back to having Training_text there fixes it without breaking anything else but it is rather wasteful. Moving the split_str() lines to message_training_setup() should also reduce some processing time on each frame if that's a valid fix for you. The variable replacement would still work, but only once, so it wouldn't ever be change *while* the message is displayed. I don't know if that's intended though and if it is then the Training_text fix should be used. It's the least problematic fix as I'm sitting here looking at it though. After testing it seems to work fine but if it's wrong then feel free to change it. EDIT2: Yeah, I'm tired, just leave me alone ;) Simply moving split_str() does all that's needed. Gotta commit and then get to the bed before I fall over. :) edited on: 05-23-05 00:15 edited on: 05-23-05 00:31 |
|
|
Fixered... I hope. |
- Anonymous
