-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx
[mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf
Of Sean Evoy
Sent: Friday, August 20, 2004 9:04
AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Managed
Build option change notification
Chris,
The
only internal client of this information was the indexer, and it stopped
listening to those notifications and switched over to using the IPathEntry
feature notifications. Since nobody is using it anymore, we can pretty much do
whatever we want with that interface, including making it more generic and have
it behave like you describe with no risk.
Sean
Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada
|
"Recoskie, Chris"
<crecoskie@xxxxxx>
Sent
by: cdt-dev-admin@xxxxxxxxxxx
08/19/2004 05:39 PM
|
Please
respond to
cdt-dev
|
|
|
To
|
<cdt-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
[cdt-dev] Managed Build option change
notification
|
|
I have to implement some features for our product that respond to
changes in the build options. However, I noticed that change events are
only being sent from ManagedBuildManager for options that will influence the
scanner.
Does
anyone foresee problems if instead it sends change events for an arbitrary
option? Right now it seems nothing in CDT implements IScannerInfoChangeListener,
which seems odd to me. How does the scanner detect changes in the build
model then if it isn’t listening to these events?
I
can’t recall if it was ever brought up in the Managed Build++ discussions
we’ve had but really this event notification stuff should become more
generic. It should send notifications on any option change and only send
a delta of those options that changed.
Opinions?
___________________________________________
Chris
Recoskie
Software
Designer
IDE
Frameworks Group
Texas
Instruments, Toronto
