🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.socket
Article #5437

Re: TIdIRC Access Violation

#5437
From: Tog
Date: Wed, 08 Sep 2004 23:55
13 lines
1506 bytes
Ok fair enough, let's assume it's NULL, well it is I guess.

But why then fire an event where I am suppose to announce a +op in a channel
and I can't tell who's being +op'ed since ATarget->Nick has no value?

How am I suppose to know who was given a +op if ATarget->Nick isn't valid.
It's not like I manually run the event, TIdIRC decides that it must run this
event based on the data received, how can it run this event without giving
me data to work with? Am I suppose to get ATarget->Nick from somewhere else
in that particular case? Is the event fired multiple times where AUser->Nick
has a value and ATarget->Nick sometimes doesn't?

Thanks!
Technical Details
Message-ID: <413f9bee@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail
References: <413f93a5$1@newsgroups.borland.com> <413f973c$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,d6069b12da25a878
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: <Tog>
Newsgroups: borland.public.cppbuilder.internet.socket
References: <413f93a5$1@newsgroups.borland.com> <413f973c$1@newsgroups.borland.com>
Subject: Re: TIdIRC Access Violation
Date: Thu, 9 Sep 2004 01:55:27 +0200
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: 83.109.19.110
Message-ID: <413f9bee@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1094687726 83.109.19.110 (8 Sep 2004 16:55:26 -0700)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail