re: about the newGUI

[Min3mat]

wheres the latest version? is it NewGUITorr5.zip?

[IMSabbel]

Just press F6 to have it when you want.
I think someone wich know about html could do it.

ah, thanks.

How about making holding shift while scrolling speed up again?

Edit:
wow, just created a local game, pressed F6, clicked on "sum", and spring created a protection fault and closed.
EDIT: It seems it has no sanity checking... it crashed if there isnt enought data available yet, for example when opening just after beginning of the game, or opening player stats before units have been killed)


Also, i cannot enter a filename when selecting not to be host. Backspace for deleting the standart "test.sdf" works, but not entering something else.

Also (2) for some reason, the game seems to be a mixture between xta and OTA after downloading the new data... Commander can build advanced plants, large berta models, but Fusions only output 1500, no immolator, ect.

[Torrasque]

wow, just created a local game, pressed F6, clicked on "sum", and spring created a protection fault and closed.

I think it happen when the game were on "press enter to start"
Certainly a div 0 error.

Also, i cannot enter a filename when selecting not to be host. Backspace for deleting the standart "test.sdf" works, but not entering something else.

It's easy to fix...I didn't change it because I don't want to break compatibility with the actual GUI.
You can always use Ctrl-C.

Also (2) for some reason, the game seems to be a mixture between xta and OTA after downloading the new data... Commander can build advanced plants, large berta models, but Fusions only output 1500, no immolator, ect.

Are you sure it is an newGui error?

[IMSabbel]

Well, im quite sure, because i created a new, clean 0.60b install and copied you files into it...
So it at least has something to do with your files (how they were compiled, which ressources, ect).


But cool, i noticed resizing of the map with middle mouse button, and it also works with the command bar (left). The only annoying thing: it just cuts off the lower area, instead of moving it into the empty space in the middle, so its not possible to create a larger minimap per hand while still being able to use the command buttons.


But how about a new version? There seems to be lots of little things fixed already, and it would help for non-redundant bug search...

ah, and .spectator doesnt seem to work when playing a demo
and you might consider some other line choice for the while team, invisible isnt that hot :D

[IMSabbel]

I added

+_release=speedup;
-_release=slowdown;

to my bindings, but it produces the strange result that _both_ + AND - slow speed down...
The Speedup binding has the same effect as the slowdown... Some internal parsing error?

[Weaver]

Torrasque, where are the graphics for your buttons? I was thinking I might have a go at making some different ones.

[Torrasque]

Weaver : Now all buttons are from button.bmp... I've got some clue to add a texture tag separatly for each button, but they are still some weird bug I must eliminat before doing this.

[Weaver]

Here's a screenie of what I've done, I'll upload the bmps if anyone wants them.

----------- Old -------------|------------ Mine -----------|------------ Edit -----------


Couldn't help myself, hence the edit.

[zwzsg]

I prefer old. Easier to read.

[Min3mat]

whats the difference between new and edit? they are both good IMO anyway

[Weaver]

whats the difference between new and edit? they are both good IMO anyway

Small things around the blue lights, made even harder to see by the jpeg compression of the SS.

[Edits]
I found a crash while exploring the interface F6>Player Stats will crash the game if used before anyone has built anything.

And a graphical bug, the check button, when selecting "share selected units" is odd.

The new GUI is pretty much unusable below 1024x768 owing to overlapping items.
[/Edits]

[CrowJuice]

I prefer old. Easier to read.

I agree with zwzsg.

[IMSabbel]

But still something has to be done.
its just button-creep. To much clutter.
(and i also thing that self-destruction shouldnt get a button)
Also, the selectors arent winners concerning usability... I mean, a button named "uncloaded" with a blue light right... does it mean click to uncloak?, ect (yeah, i know one does know it, but if you argue that way, one could leave out the gui and make it short cut only.)

Much more sensible would be a Cloaking: (On/Off) style selector, same for radar, ect.

[Weaver]

Interesting points IMS

The standing orders buttons have always shown the current state.
"Uncloaked" is pretty clear to me, what the lights show is the number of possible states. One light position lit to show the active state would do for single unit. But multiple units in a group may have different states and this was shown in Old TA by having more than one light lit and changed button text. (currently not working in this GUI)

You suggest "Cloaking On/Off" this has more ambiguity, does that mean cloaking is on or click to turn cloaking on?

What might help if we can standardise, is more light colours, so that we can reconise state from the colour as the position is less obvious at a glance. We still need to keep the text for those that like it and those that cant see all colours.

I suggest these colours;
Green = On / Active / Roam
Yellow = Return Fire / Maneuver
Red = Off / Inactive / Hold Fire or Position
We can use more colours if we need them.

The SelfD button is a little scary, I might agree on this one.

[Redfish]

I prefer old. Easier to read.

I agree with zwzsg.

And So do I agree. If you change it then make sure you can see the other options visibly, instead of using black where the square was.

[IMSabbel]

I suggest these colours;
Green = On / Active / Roam
Yellow = Return Fire / Maneuver
Red = Off / Inactive / Hold Fire or Position
We can use more colours if we need them.

The SelfD button is a little scary, I might agree on this one.

Yeah, colour coding can really help making it more intuitive.
Also, it might help to give toggle buttons different styles, by function.
Right now, every units has several switches that look the same, only with different text. So one _has_ to read the text in order not to make mistakes, which negates the whole reason why there are graphical buttons.

[CrowJuice]

What might help if we can standardise, is more light colours, so that we can reconise state from the colour as the position is less obvious at a glance. We still need to keep the text for those that like it and those that cant see all colours.

I suggest these colours;
Green = On / Active / Roam
Yellow = Return Fire / Maneuver
Red = Off / Inactive / Hold Fire or Position
We can use more colours if we need them.

Some people are colour blind(like me) so it would be kinda useless. Why not use patterns?

[Min3mat]

becasue oOTA used colours AND because there is text above it (besides all you really need to fix in your mind is which side is which i.e. left = hold pos right = roam)

[IMSabbel]

Just one little detail about th new gui (a one line fix):
It would be nice if the F6 sreen would update itself while replaying a demo (currently,you have to close and reopen for a update)

[Torrasque]

I considere all your point guys, but, for the beggining, I'll try to make the newGui acting like the current and without bug.
After being merged, I'll try to make some of your suggestions.

Saddly, I'll not really able to work on this this week
And I'll have to implement the cool new stuff in the CVS :)