Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - JanosK

Pages: [1]
1
Quote
Now the start external program way of debugging works again.
Thank you Colin - this works perfectly well!

Cheers
Janosch

2
Thank you so much Geert!

Quote
- Use Debug|Attach to Process and choose EA.exe
This procedure works for me now too - and even my Diagnostics.Debug.WriteLine() messages are appearing in the Output view again.

Earlier with VS2008 i was using the setting "Start external program" in the project properties, to start the EA.exe with my DLLs. This doesn't seem to work anymore - but anyways, connecting to the existing EA appears to be a much nicer way.

Thanks again for your nice and super-quick help!
Cheers
Janosch

3
Quote
That is what I meant by debugging.
I never had issues with that in VS2010.
Alright, so it must somehow work for me as well...

Quote
I suppose you compiled in debug mode?
Exactly. I'm running Visual Studio 2010 in administrator mode on Windows 7, 64bit. The EA version is 7.5.
To start the project, i right-click on the project and go "Debug->Start new instance" or "Debug->Step into new instance". Neither of these options work for breakpoints.

I have to admit, that the VS-world is not my world (still... but hoping). Is there maybe some elementary thing that i may have forgotten to set, activate, enable...?
For my colleague, debugging doesn't work either with the common settings under same platform conditions (Win7x64, VS2010).

Thanks a lot for your support.

4
Hi Geert,
thanks for your quick reply.

By "Debugging" i meant setting breakpoints and halting&stepping the Add-In whilst it is running inside the EA.
Is that also what you were talking about?

I can start the the Add-In from within VS2010 by attaching to the EA.exe - but i cannot halt&step the Add-In as i could with earlier VS versions. (i do not have proof for this - but i am pretty pretty sure!)

Cheers Janosch

5
Automation Interface, Add-Ins and Tools / Add-In Debugging from VS2010
« on: January 24, 2011, 11:27:38 pm »
Hi all,

I'm back to EA Add-Ins, but the development keeps going on with the Visual Studio 2010.

With the VS2005 and VS2008 i was able to both output debug messages (to the output view) and more importantly to set breakpoints and step through the Add-In code.
This all doesn't work with VS2010 now - and i don't have a clue where the problem might reside.

Are you guys able to actual debug your Add-In code with the Visual Studio 2010 and output messages - and if so, could you perhaps give me any hints so that i could get it to work as well?

I'd appreciate your help!
Cheers
Janosch

6
Automation Interface, Add-Ins and Tools / Re: Using ExportPackageXMI
« on: September 11, 2009, 11:18:07 pm »
Thank you guys,
i've submitted a bug report on the export dialog issue.
Cheers

7
Automation Interface, Add-Ins and Tools / Re: Using ExportPackageXMI
« on: September 11, 2009, 08:03:34 pm »
Hello,

do you guys know of any possibilities to not let the EA's "Export Package to XMI" dialog appear, when programmatically performing the export? We would like to perform the export in the background, but the whole process seems to be tightly joint to the dialog.

For the record:
The checkbox "Exclude EA Tagged Values" doesn't seem to be modifiable by the API. Indeed this option is an important setting to achieve UML2, which can be "understood" by the Eclipse EMF.

Cheers
Janos

8
Thanks for your support guys. It's good to find people who help, and even think about how they can help!
Cheers

9
Thanks David and Geert,
looking through the SDK was what i've been doing all day - only now i've found it, and it works beautifully!

Code: [Select]
Repository.ReloadDiagram(Repository.GetCurrentDiagram().DiagramID);
Thanks again!
Cheers Janosch

10
Hi,
thank you very much for your quick response!

Some more things arise:

First, using
"Repository.GetProjectInterface().ReloadProject();"
as you've suggested, unfortunately doesn't seem to perform the desired update. I can tell, that the project is somehow reloaded (there is some one or two seconds of processing), but the diagram itself remains unchanged. When i do the mouse-context-menu "Reload '<Diagram>'", the diagram changes.
I've tried this Project.ReloadProject() in several combinations with and without the Diagram.Update() and the DiagramObject.Update().

Second, updating the entire project isn't actually what i desire... Looking at the one or two seconds mentioned above, which it takes to reload a (mostly empty!) project, i wonder what the possibility of changing the style is actually good for in the end. Why can i change the appearance of an object, but cannot actually apply the change to the UI?

Is there no other way to redisplay a diagram, rather than reloading the entire thing?

Thanks for your help!

11
Automation Interface, Add-Ins and Tools / Diagram Update/Refresh/Reload
« on: August 18, 2009, 11:57:09 pm »
Hi there,
i'm stuck in this rather simple seeming issue of changing the appearance of diagram elements by automation. Triggered by an Add-in menu event, i'm changing the style of all DiagramObjects by doing as follows in C#:

Code: [Select]
EA.Diagram diagram = Repository.GetCurrentDiagram();
Collection objects = diagram.DiagramObjects;

foreach (Object o in objects)
{
   IDiagramObject dObject = (IDiagramObject) o;
   dObject.Style = "BCol=35723;BFol=9342520;LCol=9342520;LWth=10;";
  
   dObject.Update();
}
diagram.Update();
objects.Refresh();

The new style though is only applied to the diagram elements, when i reopen it or choose "Reload '<Diagram>'" from the tabs context-menu.

What am i doing wrong, or which "reload/update/refresh" on which elements might be missing?

By the way: I'm working with EA 7.1.831. I will have access to EA 7.5 in a couple of days.

Hints and help are much appreciated!
Thanks

Janosch

Pages: [1]