Poss bug in ABC

[harkan]

Entered an option name and added {br} at the end. Saved dat file, compiled and then opened the list in Army Builder and everything behaved as it should do. Opened the dat file in abd again, no issues, however the {br} had been replaced with a square (looks like a text version of an ascii code):

http://www.harkanironfist.co.uk/images/br_name.jpg

File functioned as it should do in AB and ABC, however when the option was edited, saved and the file saved, when compiling the data file it threw an error of invalid option name. When looking into the dat file in notepad it showed the {br} that had been replaced with the ascii code had then inserted the equivalent of /n and a new line had been put in:

http://www.harkanironfist.co.uk/images/notep.jpg

Using /n instead of {br} also created the same problem

 

[Colen]

At 05:21 PM 6/5/2005 -0400, you wrote:

>Entered an option name and added {br} at the end. Saved dat file, compiled
>and then opened the list in Army Builder and everything behaved as it
>should do. Opened the dat file in abd again, no issues, however the {br}
>had been replaced with a square (looks like a text version of an ascii code):
>
><http://www.harkanironfist.co.uk/images/br_name.jpg>http://www.harkanironfist.co.uk/images/br_name.jpg
>
>File functioned as it should do in AB and ABC, however when the option was
>edited, saved and the file saved, when compiling the data file it threw an
>error of invalid option name. When looking into the dat file in notepad it
>showed the {br} that had been replaced with the ascii code had then
>inserted the equivalent of /n and a new line had been put in:
>
><http://www.harkanironfist.co.uk/images/notep.jpg>http://www.harkanironfist.co.uk/images/notep.jpg
>
>Using /n instead of {br} also created the same problem


That's a bug (it shouldn't be converting /n or {br} to the newline
character there). However, it looks like you're trying to insert a newline
after the option name, which won't work. Can you describe what you're
trying to achieve here?

Thanks.



--
Colen McAlister (colen@wolflair.com)
Chief Engineer, Lone Wolf Development
http://www.wolflair.com/

 

[harkan]

am just trying some ideas out for Kill team in 40K, and the amount of rules (represented by individual rulesets) is significant, so to act as reminder for the user then a unit acts as wrapper for them, with options that display dependant upon the rulesets selected. However, having the option info displayed in the unit info screen was not too clear when they ran into each other seperated by a ';', so the new line was to split each one down onto it's own line to improve readability.

I have seen this used before but couldn't remember where it was for an example of it, so thought that the /n after the name shouldn't be a prob. The actual script etc does work as intended, the option info in the display info window are on seperate lines.