Vha.Chat and Vha.Net released

[madrid]

Ah word

[Sumbodykilla]

No android support :'(
Hope someone has lots of love and makes us an app

[Vhax]

No android support :'(
Hope someone has lots of love and makes us an app

There should be more love once Google stops being silly about their SDK.
Java-but-not-java and c++ without exceptions isn't exactly charming me.
Even the iPhone makes it easier for developers, and they're king of all vendor lock-ins.

[Sumbodykilla]

Would donations charm you at all?

[Vhax]

Would donations charm you at all?

Nope :P

[TheCatlady]

Hello,

was trying out the chat and got the following message:

"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Object reference not set to an instance of an object."

O.o?

I can select a channel, and type, but every few moments that message pops up again.
What's the problem?

Thanks,

Thay

[Nistrum]

Hello,

was trying out the chat and got the following message:

"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Object reference not set to an instance of an object."

O.o?

I can select a channel, and type, but every few moments that message pops up again.
What's the problem?

Thanks,

Thay

I had a similar problem, updated to a newer version of Microsoft .NET and now it works perfectly.

[Demoder]

wtb SVN update of Vha.Net.

[Vhax]

wtb SVN update of Vha.Net.

It should be all updated.
The 1.1 branch is at 1.1.2 and trunk is at 1.2.0.
There's 1 unmerged revision in the 1.1 branch, but that was just a version bump.

[Vhax]

Haven't had much time to work on 1.2 yet, so I bring you a small bugfix release.

1.1.3
- Embedded Chat.html inside the binary. This should prevent chat.html loading errors
- Forced Vha.Chat to run in 32-bit mode to prevent errors caused by badly written IE plugins (like Flash)

[Vhax]

I'm having some issues tracking a few odd errors users reported.
If you're one of those users, please upgrade to this release which contains improved error logging to help me find the error.

1.1.4
- Added error logging. If an error should occur, please share your error.log with us

[Kane-Hart]

thanks!

[Vhax]

Since 1.2 and especially 1.3 is taking quite a while to get ready, I've decided to provide a work around for the biggest issue the client currently has; readability of scripts and bot output.

By default the client will now strip all colors from scripts and bots.
This behavior can be changed by editing Config.xml.
Changes to Config.xml won't be visible until you restart the client.

1.1.5
- Upgraded to Visual Studio 2008 (still using .NET 2.0 though)
- Fixed crash error related to FriendStatusPacket
- Implemented a really basic configuration system
- Moved MaximumMessages, MaximumTexts, MaximumHistory values to Config.xml
- Added support for stripping and inverting text colors in the main window (edit Config.xml manually to access these settings)
- Added color stripping as default text style to ensure good readability for new installations

[Nakrima]

Didn't FC used to have a client like this on their website that you could use, orrrrr am I just remembering false memories (:P)

Cool app though! Looks great and functions just as well!

[Vhax]

Didn't FC used to have a client like this on their website that you could use, orrrrr am I just remembering false memories (:P)

You're right.
That actually is the base all these 3rd party applications and bots are based on.
It was a java applet that was decompiled and ported to various languages.
It would no longer work though, as the protocol went through some changes over the years.

[Octopuss]

Do you mean that the chat client is B&W from now on? Ffs? No way! I want colors.

[Vhax]

Do you mean that the chat client is B&W from now on? Ffs? No way! I want colors.

If you read all of it: the colors can be enabled again and they can be inversed (which looks more readable on a light background).
Not all colors are gone either, just those produced by bots and scripts.
Also, it's an intermediate solution till 1.3 is ready.

[Vhax]

Today's late night release is almost entirely brought to you by Demoder.
Having found the ability to create .patch files she quickly filled up the forum with many patches ranging from minor bug fixes to entire new features.
During this process I mostly worked through the patches and tweaked/reformatted the new content a bit at most.
The credit for 1.1.6 belongs entirely to Demoder.

So much for the good news though
As this release contains several new features and some of which are a bit harder to test, we decided to not call this the newest stable release.
We'll move forward safely and release 1.1.6 as a beta first.

Now without further delay, 1.1.6:
- Added support for ignoring users
- Added caching of the last used dimension, accounts and characters
- Added support for connecting through socks and http proxies (see Config.xml for -details)
- Added support for system messages (offline notifications, etc)
- Added automatic focus to the input box after logging in
- Several bug fixes and optimizations to internal parts of the libraries supporting Vha.Net

ps. Take note of the "known issues" in the main post.

[Vhax]

Demoder's coding spree rages on and it's now time to rip off the beta tag

1.1.6
- Revamped the ignore system's storage method
- Changed default ignore method to 'per account'
- Added some fixes and enhancements to the proxy support
- Hiding/showing the connect/disconnect buttons when appropriate
- Added support for using enter and escape on the character selection screen

[Garuvial]

A quick comment.

As it happened to me, I forgot to shut off the chat client when I left work yesterday and I noticed something that's not really a bug, but inconvenient at the least. The client auto-reconnects. Which in it's self isn't a bad idea but it is when it's uncontrolled.

Anyway, when I logged in on the same toon that was logged in on the chat client at work it caused a continuous logon/logoff spam in the org bot. Of course, this was my bad and shouldn't have forgotten to turn it off in the first place but still.

Now as for solutions maybe an option to turn off auto-reconnects or maybe even just a maximum amount of reconnect attempts? As it is now it apparently never stops trying to reconnect.