Known bugs in leafChat 2.0

Channel names ought to be case-insensitive, but in some places they are not. If you join a channel with 'the wrong case' (i.e. your join has different case to what the server thinks the channel's name is), this can result in problems. What usually happens in this situation is:

1) The name list won't have anyone in it (except you), until other people join
2) When people quit or part, the message will display as unhandled grey (because leafChat didn't realise that person was on the channel).

On OS X 10.5 (Java 1.4 or 1.5), remembered window sizes do not work accurately in separate windows mode. To reproduce this problem:

0) Make sure your 'interface style' is set to 'separate windows'.

1) Click the Connect button
2) Resize the Connect window so it exactly matches something else on your screen
3) Click cancel to close the window
4) Click Connect again

You'll notice that the resulting window is a bit (28 pixels) wider than it should be.

Do you use OS X 10.4? I'd like confirmation as to whether this happens there too. If I don't receive it, I'll make the fix for 10.5 only.

There have been a number of automatically-reported errors from Windows XP systems along the lines of:

Error saving script.
Failed to delete script file (filename.jar)

This doesn't appear to happen for all script files. If you get it, could you send me your existing script file (the one it couldn't delete), the .leafChatScript file for it? Thanks.

If you save a script that has an error involving a non-ASCII character, this causes a system error. For example, make a one-line command:

é=4;

You can try to enable scripts even when they have errors. This causes an error. (The system shouldn't let you try to enable the script when it has errors - clicking on the Enabled checkbox should do nothing, and it should be greyed out.)

To reproduce this problem:

1) Create a script that doesn't have errors.
2) Save it and close the editor.
3) Enable it.
4) Disable it.
5) Open the editor and make a change that causes an error.
6) Save the script and close the editor.
7) Click to enable it. After a brief pause, you'll see an error message.

An error can occur while trying to add to the full-text log index. The error will probably display as 'Error during dispatch of...'. Somewhere in the error detail it will include the following line:

Caused by: java.lang.Error: Index writes inconsistent

I have examined the code and can find no reason why this can occur, so am unable to fix it at present (unless I get a better idea). If anyone knows a reliable way to make it happen, let me know.

'Error during dispatch of leafchat.core.api.SystemStateMsg' was automatically reported; it's, to do with a NullPointerException in the toolbar.

I have examined the code and can't see why this should happen. However, for 2.1 I've changed it to check for this error condition earlier and in a more specific way so that if it happens again, I might be able to find out why.

If anyone knows how to cause this error, let me know.

It seems to be possible to type text (or use the /say command) somewhere, in some condition, and have it cause a system error. Near the bottom, the detail of this error contains the lines:

Caused by: java.lang.NullPointerException
util.xml.XML.convertMultipleSpaces(XML.java:627)

I have looked at the code and can't find anything wrong that would cause this error. However, for 2.1 I've added additional checks which should mean that an error occurs at an earlier stage in this situation, making it possible to diagnose the problem in future.

If you know how to make it happen now, let me know.

If you choose a disallowed nickname, such as _, or one that is in use, leafChat should handle it by automatically changing your nickname to a variant that isn't in use by adding _ symbols. This works. It's necessary in order to get you connected initially.

However it also applies even if you are already connected and manually typing the /nick command, which it shouldn't (you should just see the error and not have your nick changed at all). In addition, this can cause system errors in some cases.

Certain server numerics could cause errors because the program assumed there was going to be sufficient parameters.

Somebody experienced an error when clicking Cancel in this dialog. I can't figure out how it happens. If anyone can reproduce it reliably, please let me know.