Robert r. Sanders wrote:
You could try using a ThreadLocal... they kind of worry me, but I've
seen a lot of people use them for data passing when there isn't a more
straightforward way.
That only keeps an object local to the current thread, so unless these
things are actually executed in different threads I don't think
there would be any difference.
And here's the problem - the Move
macro operation is performed as the combination of the Copy and Delete
operations. So a _Copy_ macro event is fired whenever a _Move_ action
happens. Therefore, the moved resource's ID property is changed by the
Copy event handler!
Sound like a design flaw to me. I haven't seen the code in that area,
but would it not be possible to refactor out the common code from
the copy macro and call it from both macros?
The copy event could then be fired only in the copy-specific macro
(that would also call the new common function for performing the
actual copying).
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
