Hello,
I am not sure if this should go to bugs or wishlist, please feel free to change category if desired. Nevertheless it seemed like a bug to me so I placed it here for the time being.
I have noticed long time ago that TCP/IP onConnect is being called in situations where no connection was actually established. Lets say you have TCP/IP DAT configured as a Client. You are trying to connect to address that doesn’t exist, but onConnect is called right away. Shouldn’t it be called only if connection was successfully established?
Same goes for disconnect. Lets imagine you are connected to some TCP Server that shuts down. I would expect onClose to be called right away on your Client (as it is forced to disconnect from this server). This however doesn’t happen until you turn Active toggle off (which doesn’t seem right to me).
