I'm using a TUDP component for broadcasting purposes.
It works, but the component acts oddly in two ways (I guess these problems are somehow connected):
1) Before it can read/listen, it must be activated by sending something first - and there's no 'activate' procedure for it.
2) Worse: Once it _has_ been activated, it makes the application crash when shutting the app down... some error in a windows dll is reported.
Do anybody know what's wrong?