DataGridView Vertical Scrollbar crash

[Squirrelington]

I made my own Ncid client and on connect it parses and populates the History DataGridView control with the CIDLOG entries.

I've read in a few places about othr people having this problem where the program just crashes when you try to scroll vertically in the grid, I have this same problem but none of their fixes work.

Here are the 2 programs, 1 with scrollbars and 1 without.

http://www.neonblu.com/Ncid-NT/Ncid-NT.exe

http://www.neonblu.com/Ncid-NT/Ncid-NT_scrollbars.exe

There are a few command-line arguments you can pass to add or change functionality, they are as followed. (OPTIONAL)

-debug (or -debug=<level>): Enables debug mode (and if set with a value, sets debug level). Debug level range is 0-3. (OPTIONAL)

-min: Starts Ncid-NT minimized (good for starting the program with Windows).

Needs to connect to a Ncid server with at least 8 CIDLOG entires so it'll make the vertical scrollbar. Any help is appreciated, thanks in advance.

LANGUAGE: VB.NET (Framework 2.0)

Edited May 20, 2007 by FuhrerDarqueSyde

[Squirrelington]

For testing purposes I am including my Ncidd Dummy server, it accepts connections and spews the data a real Ncid server would send. The data sent is hardcoded, if you're running Ncid-NT.exe in debug mode and see "Too many clients connected", that message is fake ;).

Run the Ncidd dummy server if you dont have an ncid server, then open Ncid-NT and set the hostname and port in the Settings tab to 127.0.0.1 and 3333

Download NciddDummy: http://www.neonblu.com/Ncid-NT/NciddDummy.exe

[Squirrelington]

2537 contains a bug with the -host and -port command-line parameters, this is fixed in 2539. However, I am too lazy to upload it, so just start ncid-nt.exe and set the host and port in the settings diag. :p

If you accidentally set the Settings wrong and the program starts crashing with Unhandled exceptions (hey, its still alpha stage), navigate to HKEY_LOCAL_MACHINE/Software/Neonblu Technologies/Ncid-NT and you can change the params there for now...

Edited May 20, 2007 by FuhrerDarqueSyde

[Squirrelington]

FIXED: It was caused by Illegal Cross-thread calls to the DataGridView Control