Messages

1

General Board / Re: in brower window, how to sort diagrams before packages?

« on: June 02, 2023, 05:32:17 am »

Thanks, all.  It's that options is just missing in the SaaS version when I did the trial.  I've got a question into them about it.   It works fine on my desktop version. (16.1.1625)

2

General Board / Re: in brower window, how to sort diagrams before packages?

« on: May 27, 2023, 04:03:51 am »

I was just looking into this.  I'm taking the EA SaaS Trial using the MySQL repository, and on that instance, the diagrams are below the packages and the checkbox Geert referreed to is missing on Preferences/General.   The SaaS instance is running 16.1.1625.  Any ideas why this the case?   

3

Automation Interface, Add-Ins and Tools / Re: v16.1 - Holiday period present from Sparx Systems!

« on: December 05, 2022, 01:27:07 pm »

Nice! 

4

Automation Interface, Add-Ins and Tools / Re: 16.1 - What are the wildcards?

« on: December 05, 2022, 01:26:04 pm »

Thanks, q!  I was wondering if I was going crazy.  Perhaps I am, but not about this.   

5

Automation Interface, Add-Ins and Tools / Re: 16.1 - What are the wildcards?

« on: December 03, 2022, 07:20:52 am »

I'm just talking about the Common Searches/Simple dialog that comes up when you hit CTRL-F to find, which is the search I use 99% of the time (and I don't think I'm unusual in that respect).  I just tested this again.   In 15.2 and earlier versions using an EAPX file, the wildcard to get all elements is *.   In 16.x, it is %.    When I put #WC# in either version, it returns no results. I'm not trying to use a SQL query.   My point was  that for a simple search like that the wildcard should not be database dependent and I would argue that * is better because that's the most common wildcard that everyone knows.   (e.g. for searching file names on Windows)

6

Automation Interface, Add-Ins and Tools / Re: 16.1 - What are the wildcards?

« on: December 02, 2022, 04:39:43 pm »

Ok, there is something I'm not getting here.  What am I supposed to put in the search term if I simply want the search to return ALL elements in the model.   I put in various forms of #WC# based on what I was able to read here   https://sparxsystems.com/enterprise_architect_user_guide/16.1/the_application_desktop/creating_filters.html  and that doesn't work.   So, it looks like I need to use % when using QEA and * when I'm using EAPX.   

7

Automation Interface, Add-Ins and Tools / Re: 16.1 - What are the wildcards?

« on: December 01, 2022, 03:02:32 pm »

Thanks, everyone.  Will use the % which seems to work. Geert, you guessed correctly that I switched database types.   It seems really odd to me that this should change in the UI due to the database.  Seems to me that EA's UI should specify what the wildcard is and then do the translation behind the scenes.    (i.e. it should not change based on dataabase or driver which is not something a user should be expected to know)

8

Automation Interface, Add-Ins and Tools / 16.1 - What are the wildcards?

« on: November 28, 2022, 04:13:39 pm »

In 15.2 and previous versions, I could do a wildcard search in the "Find in Project" window by putting in a '*' in the search box.    That doesn't work in 16.1 as it searches for the string '*' in the elements.  Hmmmm. Why different? 

However using the underscore '_' DOES appear to work as wildcard.  (Don't ask how I figured this out as I think I was just lucky). 

I can't find any guidance on search wildcards in the Help, so if someone has insight on this, I would appreciate it. 

I find this really helpful for filtering searches by stereotype so, for instance, show me all the Archimate Business Processes in my model, regardless of folder.

9

Suggestions and Requests / Re: New user preference - show/hide {} element in browser

« on: November 19, 2022, 08:00:54 am »

Big +1.  Have also put in a feature requiest.  This should be something I can easily toggle from the browser panel. 

10

General Board / Re: EA16 - browser showing diagram elements under {} package

« on: November 19, 2022, 07:53:17 am »

Big +1 for this feature requests.  This pseudo folder is very much in the way, especially when walking through a model with non EA users over Teams/Zoom, etc, which is something I do all the time.   This should be a hide/show button right on the browser panel.   

11

Bugs and Issues / Re: V16.1 - Holding down CTRL key and using scroll wheel does not zoom Note text

« on: November 17, 2022, 02:40:38 pm »

Well, I heard back from the support team.    And the answer is that you need to use CTRL+SHIFT with the mouse wheel and I verified that does work.   

Not really sure why this change was made (a mystery), but there you have it.   RESOLVED,  I think.   

12

Bugs and Issues / Re: V16.1 - Holding down CTRL key and using scroll wheel does not zoom Note text

« on: November 17, 2022, 05:21:49 am »

just did. Thanks.

13

Bugs and Issues / V16.1 - Holding down CTRL key and using scroll wheel does not zoom Note text

« on: November 16, 2022, 09:47:10 pm »

In 15.2 and earlier versions, I could hold the CTRL key and use the scroll wheel to zoom up the size of the note text (and down).  Given that the defauilt text size is so small, this is a really important feature, especially when reviewing models over Teams.   But in 16 and 16.1, this does not work.  It may seem odd, but this is stopping me from going to 16.1 as I do a lot of this and readability for reviewers matters a lot.

14

General Board / Re: EA v16 invisible objects are now visible in the project browser

« on: October 17, 2021, 06:13:17 pm »

Yes, it's useful sometimes, but is there a setting to hide that folder?   Viewing and/or where it appears should be a user settting.     

15

Automation Interface, Add-Ins and Tools / Re: Anyone out there have done automatic RoadMap diagram based on TaggedValue data

« on: May 31, 2021, 10:09:32 am »

Yes, this would be very good.  I can think of a way you could layout the bars using an approximation algorithm and a few tricks, but it makes my head hurt to think about it.   For instance if you knew that the X coordinate for the start of the roadmap was 0 and you knew the X coordinate for the end of the roadmap was some other number (say 2000), then you could calculate the actualy X start and end coordinates of each bar based on a ratio of the number of days past the start of the roadmap.    That might work!