>> If the problem with current demos ini files is just related to Unicode
>> strings handling, probably an TCustomIniFile descendant with string utf8
>> encode/decode is enough.
>
> Obvious from TCustomIniFile will not work, must be descendant from
> TIniFile.
>
> TMyUnicodeIniFile=Class(TIniFile)
Scrive Arno Garrels <[EMAIL PROTECTED]>:
> > I'm against to write into the registry from a demo application.
>
> OK, so nobody likes the suggestion :(
Personally I think that registry keys should be created/removed by setup,
otherwise they will remain forever.
IIRC Microsoft guide lines (from XP
> If the problem with current demos ini files is just related to Unicode
> strings handling, probably an TCustomIniFile descendant with string utf8
> encode/decode is enough.
Obvious from TCustomIniFile will not work, must be descendant from TIniFile.
TMyUnicodeIniFile=Class(TIniFile)
public
Scrive Arno Garrels <[EMAIL PROTECTED]>:
> > I'm against to write into the registry from a demo application.
>
> OK, so nobody likes the suggestion :(
Personally I think that creation and remove of registry keys should be done by
program setups. Otherwise they will remain forever.
IIRC Microsoft
>> XML can ease the process.
>>
>
> I don't think so. XML is an heavy beast, taking a lot of code and power. I
> don't like it for that purpose.
Just one idea to implement the ini sections handling, without the need
to write parsing code.
It's heavy, but to deal with these little ini files
>>> That's IMO not worth the effort, I was searching for a very simple
>>> solution that took not more than a few minutes to change everything.
>> What about writing a new TIcsIniFile doing the job ?
>> Would be enough to search&replace TIniFile by TIcsIniFile.
>> TIcsIniFile or TUnicodeIniFile
>> That's IMO not worth the effort, I was searching for a very simple
>> solution that took not more than a few minutes to change everything.
>>
>
> What about writing a new TIcsIniFile doing the job ?
> Would be enough to search&replace TIniFile by TIcsIniFile.
>
> TIcsIniFile or TUnicodeIn
>> I agree with Angus points.
>> As work around, can you transform the unicode strings to
>> UTF-8 before write it into the ini file?
> That's IMO not worth the effort, I was searching for a very simple
> solution that took not more than a few minutes to change everything.
What about writing a
> I'm against to write into the registry from a demo application.
OK, so nobody likes the suggestion :(
> I agree with Angus points.
> As work around, can you transform the unicode strings to UTF-8 before
> write it into the ini file?
That's IMO not worth the effort, I was searching for a very s
[EMAIL PROTECTED] wrote:
> The procedure "IsAddressValid" in the ICS demo project "HttpChk" works
> well to check the validity of a URL, but it is very laggy. If you
> want to do checks on multiple websites it is much too lengthy/laggy.
> Is there a better solution for checking the validity of a UR
10 matches
Mail list logo
