Decending from TService 1

[jpGt]

thread102-1444438

Hi,
The above thread discusses attempts to create and use a descendant of TService. While the thread provides a workaround, it doesn’t really provide a solution.

I notice components such SvCom take care of this job fairly well, any ideas how they fool the designer to open up a descendant of TService.

I’ve had a go myself at creating a descendant and it works fine at runtime, but not design time, keeps moaning about DisplayName property can’t be found when it’s clearly in the published property list.

 

[whosrdaddy]

I guess it would be better to write a new TService component (TMyService) without descending it from TService.
Just copy the original code, rename to the new component name and add the needed changes should do the trick.
I have never found any reason to do this as I use the TService as a wrapper around the real application, it just sparks my custom threads and stops them when the service is stopped. This way I can reuse the code, as it is only the thread that changes.

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[jpGt]

I sorted it out now...

RegisterCustomModule( ... )

Allows the IDE to pick up the extended use of the DataModule

 

[whosrdaddy]

ok then!
star for you, didn't know about that one...

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!