Starlight 1.2 Released

[Snrrrub]

Starlight 1.2 is now available for download on my site: Starlight 1.2

 

2008-07-26
Release 1.2

	- fixed bug where application would become unresponsive if the internet connection
	  was broken
	- added chat logging (saved to: data/logs/session.log)
	- added a notify list: when a message containing one of the notify strings is
	  received, the icon changes color and the application flashes in the taskbar
	- the zone selection is now maintained after receiving updates from the directory server
	- added a dialog box to display Continuum-style custom login errors
	- added ?ignore command - use ?ignore add <name> and ?ignore remove <name> to add and
	  remove players from the ignore list
	- icon changes color in taskbar and system tray when a private message is received
	  and the window is not focused
	- expands %selfname, %tickname, and %squad
	- added option to not display timestamps
	- added enter/leave messages
	- added player kill messages
	- displays player's squad in player list and allows sorting by name or squad
	- added registration form for new users - the lack of registration form prevented
	  the creation of new accounts on the SSC biller in previous versions (thanks to
	  CRe> for pointing this out)
	- fixed CRe>'s email address in About dialog
	- upgrades to the underlying control protocol (much more efficient - especially
	  on upgraded ASSS servers)

 

-Snrrrub

[L.C.]

I think I was able to get Starlight to crash when I hit Connect when it was already trying to connect.

 

EDIT :: But this version is a significant improvement over the bugs in 1.1 that prevented me from being able to use it. <_< Idling in Alpha SVS now.

 

EDIT2 :: Opening up Preferences while Starlight is connected or connecting (both ways) will crash the program. Summary below:

 

Bugs:

- Program crash when you select "Connect" when Starlight is already trying to connect.

- Program crash when you try to open Preferences when Starlight is connecting and is connected. (note: doesn't always work)

- Starlight does not automatically connect when launched, and most of the time when you click Connect the program will crash.

- Sometimes you must first his disconnect and then connect when you first launch Starlight to prevent a crash.

- If you leave Starlight open long enough when you first launch it, you will be unable to connect because the program will crash on attempt.

- If I maximize my Starlight window, then simply hit the minimize button in the top right hand corner of the window/screen, and then bring Starlight back up -- it will reset the window size to default height/width (and it animates it when it resizes the window from maximized to default).

 

Security Issues:

- User password in config.dat is printed raw / human readable.

 

Suggestions:

- When you cross-zone/arena private message with ::, your message will show up as "[12:06:35] L.C.> snrrrub" (in green) rather than the way it would appear if you messaged someone through Continuum (too lazy to provide example).

- There should be a notification or message in the chat that would indicate when the disconnect/connect button was hit, and if Starlight got disconnected or is trying to connect or retrying the connection, etc.

 

 

This is the "crash" error window. Same window comes up on all crashes.

 

EDIT3 :: Disabling NOD32 seemed to solve the crash problems. I can't use Starlight (or atleast very easily) if I'm required to disable programs. :\

 

EDIT4 :: Nevermind -- I don't know what is causing those crashes. I re-enabled NOD32 and Starlight is co-operating now (I can't replicate the crashes). This is mind boggling.

Edited July 27, 2008 by L.C.

[Snrrrub]

Having spoken with L.C., it seems that there's some poor interaction between some application(s) installed on his machine and GTK+. If anyone else is finding Starlight unstable, please let me know so that we can find out which application is causing the instability. If you happen to be running NOD32 and have no issues running Starlight, do let me know so that we can eliminate that possibility.

 

-Snrrrub

[L.C.]

Two other bugs I found:

- Whenever I get disconnected, Starlight never attempts to reconnect

- Sometimes when I would get disconnected, Starlight doesn't even realize that and thinks it's connected. Look at the attached screenshot below for an example -- examine the time stamps.

 

[Snrrrub]

Whenever I get disconnected, Starlight never attempts to reconnect

 

This is not a bug, it is intended behaviour. If you were banned or /*killed you really don't want to exacerbate the situation by attempting more logins. This is not an IRC client.

 

Sometimes when I would get disconnected, Starlight doesn't even realize that and thinks it's connected. Look at the attached screenshot below for an example -- examine the time stamps.

 

I am aware of this issue - it happens when there's enough packetloss that the server has to disconnect you but the disconnect packets don't make it to the client.

 

As it stands, the above issue is the only known bug and will be fixed in subsequent releases.

 

-Snrrrub

[rootbear75]

well if banning or killing is the issue, have starlight attempt to reconnect at least once, and if it notices a "you are banned" or "you are locked" message, then do not attempt to reconnect anymore.

And also have a ?reconnect command (in case some people are too lazy to click)

[L.C.]

This is not a bug, it is intended behaviour. If you were banned or /*killed you really don't want to exacerbate the situation by attempting more logins. This is not an IRC client.

Then it should be a feature.

[PoLiX]

Lookin good...

 

And to answer LC's ?message. It has been thought of before long ago and tried. It did work, but had a lot of conflicts to come around. I again brought it up a few years ago, but noone ever tried, or showed enough interest in it. Plus it is actually rather easy to get SSC now, so what is the point anymore. There is enough SSC hosts out there willing to host zones, and there is very little requirement compared to the past to get SSC.

[tcsoccerman]

howabout a column on the listbox to go along with the player name and the player squad. this way i know who is playing and who is in spec.

[L.C.]

And to answer LC's ?message.

Which ?message? I don't recall sending anyone but Snrrrub a ?message lately.

[CRe]

The ?message in your screenshot

[Samapico]

And to answer LC's ?message.

Which ?message? I don't recall sending anyone but Snrrrub a ?message lately.

 

 

The ?message in your screenshot

^^

[L.C.]

Oh, haha. I had images disabled, which is why I wasn't sure of what you were referring to (forgot that I even attached an image!).

[rootbear75]

I cant send / by itself (like to page someone (make a beep on their client))

or '

or //

 

"

and ? work fine

Edited August 9, 2008 by rootbear75

[rootbear75]

It seems that when i File -> Connect, starlight crashes and closes out

[Snrrrub]

rootbear: Starlight was functioning correctly before, right? Did you install any new applications (in particular, AV programs such as NOD32) recently? I've found that some antivirus applications and GTK+ have some poor interactions with the same outcome as you described.

 

-Snrrrub

[rootbear75]

no new applications

now its working.. wtf

Edited August 14, 2008 by rootbear75

[L.C.]

Hrm, now Starlight seems to work perfectly fine after "repairing XP" once moving my harddrive to my new machine. I also did notice that the longer Starlight was on my system, the less the crashes seemed to occur. O_o Either that or a simple repair of XP fixed it (either because of my new machine or because my installation of XP Student was getting hazy).

[»Purge]

Has development ceased? This project looks pretty dormant now.

[CRe]

Snrrrubs been working on his biller