Thread: [Doubt]Connections are down ? TServerSocket

My ListView1 of connections reverse is going to send wrong information to the command pc.

I discovered that when you remove the item of idle connections that conflict occurs.

ItemIndex = passes the selected item to the low

how can I make tserversocket renew their connections in order to listview1 ?

my adivce: Fuck learning tserversocket and start with threads and winsock API. Indexing conections is a bad idea.

Originally Posted by KriPpLer

my adivce: Fuck learning tserversocket and start with threads and winsock API. Indexing conections is a bad idea.

For now I will finish the project with TserverSocket


Resolved

Solution

ServerSocket1.Socket.Connections[Number of connection removed].Destroy;

my adivce: Fuck learning tserversocket and start with threads and winsock API. Indexing conections is a bad idea.

I shall follow the advice of the master :p

@Krippler

What does threads have over indexing then?

p.s please dont shout at me you will make me cry you know .

you will make me cry you know

:p
I want to know that too...
Cus i dont feel like writing alot of codes like in ur example..
Thats alot of code for something simple like that...
With the SockComp u can do the same thing with ALOT less code..

Originally Posted by acidrain

@Krippler

What does threads have over indexing then?

p.s please dont shout at me you will make me cry you know .

Cuz with threads you can use pointers to threaded objects (Its better than an array) instead of looping though a list of connections which is like I said: a bad idea because its buggy. With Threading and classes, you can do things a lot faster with less code. This way you can directly send/manipulate to the selected TListItems object....

As long as i dont have to use ListView1.ItemIndex;
:p
That gets on my nerves...
When I use an inputbox, it sends the data to THe ItemIndex but when u open an inputbox the victim is no longer highlighted so it does not work :\