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 - qwerty

Pages: 1 ... 533 534 [535] 536 537 ... 625
8011
This is simply not possible. TVs are created along with an element creation.

q.

8012
Automation Interface, Add-Ins and Tools / Re: Import Images to EA
« on: August 01, 2014, 08:04:50 pm »
You can create an XML file and use the import reference data. Or you can fiddle around with the table t_image directly. Since the import reference data (still?) has its flaws regarding the reference number I would recommend to put images in t_image directly.

q.

8013
It should be a bit easier when using sub-shapes but that's just a marginal difference. IIRC there's a sample script in the help which looks a bit like a bar graph.

q.

8014
You can also find that info on page 14 of my Inside book.

q.

8015
Maybe via copy/paste. I don't know if Windoze offers a method to mimic a  copy operation so you could inspect the paste buffer.

q.

8016
Thanks for verifying that, Simon. I just wrote those lines out of my head without verification :-[

q.

8017
Code: [Select]
Element.ParentID = Package.PackageID // Package is the new parent
Element.Update()
q.

8018
Altering the MDG does not change the existing TVs for elements created from the MDG. If you Synch the element/MDG EA will add missing TVs but it will not remove existing ones. If you want that you need to do it either manually or by using a script.

q.

8019
I (AFAIR) reported that as a bug quite a while ago. So thanks for posting the solution. I won't call it workaround. It's like what Geert said. You can't wait for an official solution. So you have to build your own.

q.

8020
Automation Interface, Add-Ins and Tools / Re: Add-in Error
« on: July 14, 2014, 06:09:05 pm »
This just tells you: "You made an error. Good luck in hunting for it. Your Sparx developer team."

Honestly, I hate it. There's nothing one could do to help you except crossing fingers.

q.

8021
Well, the diagram filters are some EA functionally which (AFAIK) is not available from the APi. Setting an element invisible in the "normal" API context is that you remove it from the diagram. If you want to dynamically hide and show elements you need some external storage where you keep the original elements/positions.

Alternatively you could ask for an extension of the API.

q.

8022
Quote
Thank you Helmut,

surely this works for Fade and Grey scale so far,
but is there a specific style setting to hide Elements?

Greetings
Dan

"Hidden elements" are just no present on the diagram :D Just delete them.

q.

8023
The TVs from MDGs have some extra data in t_xref and it's a bit of black magic behind that. You might be able to recognize them. Just create a MDG stereo in an empty repos  and look into t_xref.

q.

8024
Code: [Select]
objElement.TaggedValues.Analyst = strUserwon't work. You need to iterate through the TaggedValues collection and compare for
Code: [Select]
objElement.TaggedValues.Name == strUser or
Code: [Select]
objElement.TaggedValues.Name == "Analyst" &&
objElement.TaggedValues.Notes == strUser


(You likely need to adapt for VB syntax)

q.

8025
I guess you would need to take the muddy path and somehow synch in your code with OnPostNewDiagram. This is probably going to be a PITA.

q.

Pages: 1 ... 533 534 [535] 536 537 ... 625