Oro06 wrote:
same for me,
you should deactivate smartlinking
Is the windows unit sufficiently cleaned up, that it can used without
smartlinking?
At least on windows 2k it isn't, because it contains windows xp
declarations.
Vincent.
___
Oro06 wrote:
same for me,
you should deactivate smartlinking
Is the windows unit sufficiently cleaned up, that it can used without
smartlinking?
At least on windows 2k it isn't, because it contains windows xp
declarations.
Fixed. There was some old code left for smartlinking. This is
Vincent Snijders wrote:
Oro06 wrote:
same for me,
you should deactivate smartlinking
Is the windows unit sufficiently cleaned up, that it can used without
smartlinking?
i've tested on 2003SE, HP/rz3715 , hx4700 and the arm-wince emulator from ms
it's ok for them but you're right it
On Wednesday 26 April 2006 00.43, Joost van der Sluis wrote:
Keep me informed.
Ik you find something that doesn't sound logical to you, just say so.
One problem is in internalfirst.
Old:
procedure TBufDataset.InternalFirst;
begin
FBCurrentRecord := -1;
FIsEOF := false;
end;
New:
On 4/27/06, Oro06 [EMAIL PROTECTED] wrote:
Is the windows unit sufficiently cleaned up, that it can used without
smartlinking?
i've tested on 2003SE, HP/rz3715 , hx4700 and the arm-wince emulator from ms
it's ok for them but you're right it could be a pb on other plateforms
(older wince
Hi.
Michael, I agree with you for the separation of concerns.
The new design use :
TAbstractTransport for the transport layer
( specialization could be HTTP, TCP, ...).
TAbstractFormater for the serialization of content
( specialization could be SOAP, XML-RPC, custom
