I don't know if others have reported this one yet, but I am consistently getting an error that shuts down the entire program. It reads: Gdk-Error . file gdkgc-win32.c: line 924 (gdk_gc_predraw): assertion failed: (data->xgc == NULL) aborting... .
It has appeared as I was trading, or in cases where I attempt to go into a game that has a different universe size than what I specified when I opened the connection. It has also popped up when I tried to get my ship information from the game.
On another note, many function keys in this version don't seem to work at all, but I'm assuming that this is because it is the latest beta and these functions aren't completed yet. Aside from this one particularly annoying bug, this program appears to be shaping up into a good TW helper.

John:

I see you're using the Windows version of ATTAC. Which version of Windows are you using tho? Win95/98/NT/2k/ME?

GTK for windows still has a few problems, but we have worked our way out of all of them so far.

As for the internal scripts... you're right, they don't work right now because this is still in beta. In fact, some of those buttons may temporally disappear in the next beta so we can work on getting script packs working properly.

-Peanut

Script Packs? What is this? Are you not going to include all the functionality that was previously included in ATTAC? Or are you going to sell different script packs? and if this was the case, I have to ask WHY?

-Adam

We are not selling the script packs. They are part of attac. The script pack will be the internal scripts. the reason we are doing it this way is so that if we update any script... you dont have to redownload everything again. just download the small script pack and install it and it will update all the internal attac scripts.
earth.

Question, with v4, how about the ability to either override a built in script or change/modify the script in the pack to tweak scripts? I have scripts I wrote that I use instead of the built in ones and would like to point the menu's original one to mine instead of using the macro..... Now that I am a roll on this one, how about a customizable toolbar that we can link to our scripts so they are just one clickity click (just one click please EXPL: Hunt For The Red October "...give me one ping please...") away.

Also how about the ability to write in the message center like say:

ATTAC_MsgCenter("I like to read text that I dont have to scrollback to but dont want to use a notify or pop-up message box of any kind and since the ATTAC Message Center is there, why not use that?",LIME)



Thanks,
Durken

well... basically, the internal script pack will be a seperate file. We will also be distributing a utility so you can create your own script packs. So technically, you can overwrite one of our scripts with yours, but it isnt 100% finalized.
once we finish the main stuff, we can add a section to link your own scripts to the buttons (maybe)
in v4, ALL scripts and data use the message center.
earth.

A quick clarification here. This means that ZocNotify and ATTAC_Message use the Message Center. ATTAC_Message always did, but we also make ZocNotify use the message center. I also think Say works the same way, but I'd need to check the source code to be sure. I know script errors go to the message center, so I'm pretty sure say does too.

If you would like the ability to make your own "custom" message headers and colors, that can easily be added when I don't feel like coding what I'm suppose to.

Peanut

Kewl!

Thanks!
Durken.

Bravo!

I hope the (maybe) becomes implemented as that would make me happy and maybe some others..

Thanks!
Durken

Just to let you know, ATTAC_Message has been updated in beta 3 to have the following behavior...

ATTAC_Message(Message, Header, Forecolor, Backcolor, Color_Type)

The defaults for missing parameters are as follows:

Header -> "SCRIPT"
Forecolor -> "GREEN"
Backcolor -> "BLACK"
Color_Type -> "BOLD"

Possible values for Forecolor and Backcolor
"BLACK"
"RED"
"GREEN"
"YELLOW"
"BLUE"
"MAGENTA"
"CYAN"
"WHITE"

Possible values for Color_Type
"NORMAL"
"BOLD"

If the color combo or the color type is not from the list above, it'll just ignore you and use the default.

You can leave any of the new parameters out so long as you include everything up to where you left off. IE, ATTAC_Message(Message, Forecolor, Backcolor) is not valid because you left out the Header, but leaving off Color_Type is OK.

This will put the following in your message center...

[Header] Message

In the color combo Forecolor (Bold or Normal), Backcolor.

Again, this is for beta 3. I don't wanna hear that it doesn't work in beta 2.

That's it for now. Ta Ta!
-Peanut

SWEET!

I should have an update for the Linux thread soon.


Thanks!
Durken

I've gotten this error every time i've run tw-attac under WinNT...