> I have a similar AV issue relating to Application.ProcessMessages;
If you have an AV with a call to process messages, it simply means that one
event handler is bugged.
Events handler are like subroutines called from ProcessMessages.
> unfortunately, i absolutely need to call a.pm (because my a
Hello David,
Best is to start a new thread. Many modern email readers can sort on
thread, so people not interested in this threaed will not see your
message. Anyway I deleted followup so now it should be a new thread.
> Does ICS need to call a.pm? can i tell it not to, and let me do it?
Ics need
Hello!
> Yes, I'm going to use such long delimiter because I need to send binary
> data...
If you're sending binary data, don't play with delimiters, but send the
data size first (as a 4-byte longint), then actual data. Client first waits
for data size, then waits for the data_size bytes and stor
I have a similar AV issue relating to Application.ProcessMessages;
unfortunately, i absolutely need to call a.pm (because my app does other
work as well as TCP stuff)
and it is in a base class that I _can not change_
Does ICS need to call a.pm? can i tell it not to, and let me do it?
David
-
Hello Widita,
> Those access violations never happened when LineMode is false...
> Does anyone know the solution for this problem?
LineMode True or False has on itself nothing to do with AV. So on base
on this information nobody can give solution. There is something wrong
with your code but witho
Those access violations never happened when LineMode is false...
Does anyone know the solution for this problem?
I've converted my binary data to hexadecimals string (twice size) but safer
in converting... the access violation shouldn't be in the conversion
the delimiter is #13#10
On 2/21/0
On 2/21/06, Francois Piette <[EMAIL PROTECTED]> wrote:
>
> > Hello, somebody, help me...
> > after changing my application to line mode (binary send using line mode,
> > using 4 bytes of unique delimiter)
> >
> > my application keeps giving me Access Violation Message
> > "0x00406645:write of addes
Arno Garrels a écrit :
> Or we change TCustomSocksWSocket.SetSocksLevel?
>
> procedure TCustomSocksWSocket.SetSocksLevel(newValue : String);
> begin
> if State <> wsClosed then begin
> RaiseException('Can''t change socks level if not closed');
> Exit;
> end;
> if newVal
Or we change TCustomSocksWSocket.SetSocksLevel?
procedure TCustomSocksWSocket.SetSocksLevel(newValue : String);
begin
if State <> wsClosed then begin
RaiseException('Can''t change socks level if not closed');
Exit;
end;
if newValue = '' then <==
newValue := '5';
Guillaume MAISON wrote:
>
> And, this is the strangest part, i have the ProcHttpSocketError which is
> triggered, due to an exception which is in WSocket :
>
> procedure TCustomSocksWSocket.SetSocksLevel(newValue : String);
> begin
> if State <> wsClosed then begin
> RaiseException
Arno Garrels a écrit :
> Guillaume MAISON wrote:
>> In that case, the property SocksLevel should be initialized at the
>> component creation with a value. Which is not the case in the
>> source code... As i've not changed my code...
>
> Strange I don't have that problem. It is assigned default va
11 matches
Mail list logo
