Colored Maptitle GUI 1.1

Papriko | 2012-02-05 18:51

Blurb A second attempt of my small GUI for coloring maptitles and other strings

Detailed description

I tried to improve the terrible thing I uploaded the last time with this name.
The installation is pretty easy. Download the file, copy it into the main directory of Sauerbraten and add the line "exec coloredmaptitle.cfg" to your autoexec. In case you still have the old one, just overwrite it.
Changes:

- Instead of wasting 8 variables, you have now a single command called strcol. Description is ingame

- The buttons are not copy-pasted anymore line per line, instead it is a compact looplist

- Added a new button to read the maptitle back into the GUI

- Changed the order of buttons

- Updated the ingame description according to the changes

- Input field is not limited anymore

Config file coloredmaptitle.cfg (2.41 KB)

Rating

points

(0 votes)

Comments

RaZgRiZ | 2012-02-05 19:06

I don't understand why people are so obsessed over using command sets in place of the ^f#. It's the simplest you can get, and it saves space as well, so why is it so hard to comprehend? Why would anyone sane waste 8 variables for stupid color codes anyway?

Also, why do people still do this with guifields: [$var =]
What the hell is it supposed to accomplish, nullify the value of whatever 'var' contains? You're merely creating new, blank, useless aliases like that! It's retarded and pisses me off. >:|

Papriko | 2012-02-05 20:18

1. When I tried it with ^f directly ingame, it didn't work, so injected it via script. Ironically it did now after trying once more when I read your comment. I'll still leave it in the cfg.

2. The variables were what I used before the strcol command. It were 8 vars which have been added via concat. Has been quite stupid, I know, but I did not know about lists at that point. Now I have a single list the GUI uses and the command doesn't need anything at all.

3. That with the GUI fields I really didn't know, by that I used other scripts as orientation where it was like that. Gotta change that part after this comment.

srbs | 2012-02-06 03:58

"Also, why do people still do this with guifields: [$var =]"
That shit pisses me off to, and I wonder what idiot started it.

Suicizer | 2012-02-06 17:45

It doesn't sounds that illogical to me. I would say your attempting to allocate a var, but that probably isn't what it really is =P.

So any (noob-style) explanation how it should be done and what it actually does in this way?

RaZgRiZ | 2012-02-06 18:38

It shouldn't be done. There's no reason it should be done. If there is, it's wrong.

Chaos | 2012-02-06 20:06

It's not wrong in the sense that it causes errors in the script, it just doesn't serve any purpose so there's no point in including it.

srbs | 2012-02-07 06:48

Lets say that the user types this into the field (non quotes):
"hi there ^f6Suicizer"

The body of the guifield is then executed. (human-understandable steps the compiler/interpreter takes)
1. $var =
2. alias $var
3. alias "hi there ^f6Suicizer"

Now there exists a variable called "hi there ^f6Suicizer".
See the problem now?

Note that that variable will be loaded & saved until it is removed from config.cfg along with every other combination of characters the user has ever entered in that field.
If you haven't seen the problem yet, how about now?

Here is a fun one:
In SVN, integers & floats are no longer alias-able, so (alias 54 "hi") will not work.
If a guifield that does that BS is a number field, guess what? The user will get errors every time they try to type in a number.
How bout now?

srbs

Suicizer | 2012-02-07 18:39

So actually your saying the "$var =" should be on another line, instead after "guifields:"?

Like,

guifields: $var
$var = [say "I'm a noob at scripting."]

RaZgRiZ | 2012-02-07 20:31

Shut up.

Suicizer | 2012-02-07 21:39

Never, until I finally understand the logical part of cubescript. So what's wrong about that 0.0?

srbs | 2012-02-08 06:43

That is effectively doing the same thing.
Correct behaviour is:

guifield 10 var

guifield 10 var [ echo var changed to $var ]

or something in the body that has no relation to creating variables of the field's variable.

Suicizer | 2012-02-08 20:04

Anyone can slap me harder in the face then I can do myself? As Razgriz advised me to do so, just before reading it again while thinking about how it works.

What's the "10 var" supposed to mean in this way?

srbs | 2012-02-09 00:18

The proper arguments for guifield are:
guifield <length> <variable> <body>

So, guifield 10 var [ echo $var ]
would b a field with a default length of 10, uses var to store the data & executes [ echo $var ] when the user changes the value.

User login

Navigation

Users on Quadropolis