Rather than at the session level I would prefer they be on the connection
level.
This should make your job a little easier. Keep in mind this is the default
and that the script or statement component will still be able to override
the default set on the connection.

The reason you put a IsStored function in the stored clause of a property
declaration is so that you can suppress the default condition from being
written into the DFM. This not only save on EXE size but it also increases
form load time.

Being a component developer entails thinking of things from a lot of
different angles...

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Don Schoeman" <ds@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, July 20, 2001 3:58 AM
Subject: RE: [IBO] TIB_Script macros


> I've finished the changes to the latest code to incorporate string based
> macro start/end properties, except for the session stuff.
>
> I'd just like to know a few things before I jump in and add the properties
> to a session:
>
> 1) How does a session propagate changed properties to components linked to
> the session and what would be the best way to incorporate this into
> TIB_Script.
>
> 2) Question for Jason: Since the MacroStart and MacroEnd are published
> properties I don't see a reason to store it manually, Delphi should take
> care of that. Unless I need to use it for some reason to store it's state
> within a session. Do I?
>
> Thanks in advance for any help.
>
> Best Regards,
> Don Schoeman
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>