Project.Activate event is missing

[Mike]

I need to know when the user has selected a different project, either by
opening one from disk or changing windows in Project. I see in the developer
reference that there is Activate event, but I can't find it with intellisense
(I am using c#). There is a Deactivate event but it doesn't produce the
desired result, that is - to know that a different project is currently being
displayed.

Regards

 

[Jack Dahlgren]

Going from memory... I think activate is at the application level.
Do you want to trap for when the user switches windows or are you just
checking to see which project is active?

I don't have an answer for the first situation, but you could check to see
if the project you are working on is the activeproject. Or you can set the
project you want as the active one:

Sub setFirstProjectAsActive()
WindowActivate WindowName:=Projects(1)
End Sub

I'm sure there is some way using system calls to find out which window is
which but I am not experienced in that sort of thing.

-Jack Dahlgren

 

[Mike]

JacK;

Here is a link to the Event documentation and it appears to be at the
Project level:
http://msdn2.microsoft.com/en-us/library/bb209862.aspx. I am guessing that
changing windows is the same as changing projects unless a project is open in
more than one window. I am finding that making the addin robust is a bit
challenging.

 

[Adam Behrle]

Hi Mike,

I ran into this in the past as well. Check out my post titled
"Catching WindowActivate From .NET".

Or a link:

http://groups.google.com/group/micr...8/002368f595a85c29?lnk=st&q=#002368f595a85c29

Hope that helps!

Adam

 

[Scudder]

Mike ~ A s you've found coding C# Interop is less than perfect, I therefore
tend to prototype in VB6 (even though it's no longer supported), then
complete the work in C#.

I know this may sound like double the work, but it does save hours of
wrestling with C# correct casts and all that fun stuff. VB.Net is of course
really the weapon of choice for Interop since it is the more natural language
but like you I took the C# path.

Think of VB6 as your Meta code.