[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-core-dev] Special notification rules need for move/rename/delete hooks?
|
The move/delete hook is not permitted to modify anything in the workspace
apart from the very carefully scoped task it is given. The only way to
modify the resource tree from the move/delete hook is via the IResourceTree
callback. That's why all the IMoveDelete hook API methods have the
following paragraph:
* The implementation of this method runs "below" the resources API
and is
* therefore very restricted in what resource API method it can call.
The
* list of useable methods includes most resource operations that
read but
* do not update the resource tree; resource operations that modify
* resources and trigger deltas must not be called from within the
dynamic
* scope of the invocation of this method.
* </p>
Can you explain a bit more what you're trying to do, and why you need to
modify parents of moved/deleted resources?
"Hack, Peter"
<PHack@xxxxxxxxxxxx> To: "'platform-core-dev@xxxxxxxxxxx'"
Sent by: <platform-core-dev@xxxxxxxxxxx>
platform-core-dev-admin@ cc:
eclipse.org Subject: [platform-core-dev] Special notification rules need for
move/rename/delete hooks?
11/07/2002 01:55 PM
Please respond to
platform-core-dev
If a move/rename/delete hook (from a Team provider) modifies a
directory/file that's not explicitly passed in to the hook (ex. the parent
directory of the file being moved/renamed/deleted), what are the
appropriate rules and mechanism to use to provide notification of That
side-effect change? I don't know if this has to be dealt with as a special
case
