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 - Paolo F Cantoni

Pages: 1 2 3 [4] 5 6 ... 415
Bugs and Issues / Re: Spurious Tagged Value types (non-enabled MDGs)
« on: August 27, 2018, 04:55:42 pm »
I usually remove almost all that MDG blurb in EA's MDG folder.

Yeah,  I may have to resort to that, but there are some downsides.  I'll await KP's response.


Bugs and Issues / Re: Spurious Tagged Value types (non-enabled MDGs)
« on: August 27, 2018, 09:53:15 am »
EA 14 behaves slightly differently to previous versions with regard to disabled technologies. In EA 14, the disabled technologies are still loaded into memory but are ignored depending on context and/or perspective. This looks like a place where disabled technologies should probably be ignored but aren't. I'd say it's worth a bug report.
Bug report sent.

We disable almost ALL the Sparx provided MDGs to get our EA instances to start faster (in the past versions).  Your comment about loading all the disabled technologies into memory is, therefore, concerning from that aspect.  I guess it's the enabling that takes the time, not the loading and so it should still be faster.  However, I note that EA 14 feels as though it's slower to load but I've also changed machines so that "muddies the waters".  Have you done any timing tests?


Bugs and Issues / Spurious Tagged Value types (non-enabled MDGs)
« on: August 23, 2018, 05:14:22 pm »
I've suddenly (b1425) got Tagged Value types from non-enabled MDGs appearing in my Tagged Value drop-down - for example, DMN1.1::*.  First time I've added some tagged values for a while.

They're not in t_propertytypes (not unexpectedly) and the applicable MDGs are disabled in the Specialize dialog.

How can I get rid of them?  Is it a bug that they are appearing?


Uml Process / Re: Icons on Use Case and generated Sequence Diagrams
« on: August 23, 2018, 09:34:49 am »
Hi Hotdog,
The approach we take when EA insists on displaying an icon that is not what we want is to create a rectangle with the same fill colour as the main shape over the top of the offending icon and then draw ours over the top as a decoration.


Bugs and Issues / Re: Diagram element Align keyboard shortcut don't work
« on: August 22, 2018, 09:36:53 am »
Rotate the screen? Does it have servos?
Probably you have some Windoze settings that capture the key combination.

IIRC it is the display chipset software, not native windows.  Most have configurable key combinations.  There seems to be an unofficial convention tho for what the defaults are.  It may even be in the WHQL specs somewhere.

We've had a lot of fun when people leave their machines unlocked by software rotating one monitor, physically rotating the other, and changing their mouse to left-handed.
Remind me not to let you near my desk at work!  Never mind losing the relationships window in multi-screen mode...   ;D


Connect a second monitor.

I already have 3!  The window is NOT on any of them!


Related to this topic,  I seem to have lost the Relationships Window off-screen.  How can I get just this window back onto a visible screen without affecting the others?

I tried "futzing" with the workspace setting file from a Workspace where the Relationship window was visible and on-screen but to no avail...


In the immortal words of the advertisement...  "But wait, there's more!"

If you now try to move/resize the populated window it reverts to the unscaled version!



Are you saying that all displays are running at 200% DPI scaling, or are you running mixed scaling?
Mixed scaling - the Desktop screens are running at 100%

But in a case of PURE EAUI, while the windows are "empty", you see the effect I mentioned in the OP.  I had EA open but without a repository open.  BUT, if you then actually open and use the repository and populate the window with REAL data, it miraculously scales and populates correctly!  This is also true of the other windows I tested.

Without EAUI, life would be SO boring (and productive)!  ;)


I've just got a new Surface Book 2 (under Windows 10) and use Sparx with 3 screens, two Desktop screens @ 1680x1050 and the 13.5" Surface book 2 @ 3000x2000 (with scaling set at the recommended 200%).

Most apps handle this pretty OK.  Moving windows between screens adjusts the size of the window accordingly.

However, EA (as usual) does something unexpected.  If I move the Element Browser window (for example) from the Desktop screen to the Surface Book Screen, the physical size reduces dramatically (in order to maintain the pixel size) and a "ghost" window is also created - slightly lower and to the right at what looks like the correct size if the window was being adjusted for the scaling.  The ghost window stops me positioning the window in the correct place and the real window is too small to read without the magnifier!

Anyone else seeing this at high resolutions with multiple screens?


General Board / Re: Aggregates connector is shown the wrong way around
« on: August 20, 2018, 09:54:03 am »
Like or life?

It should have been, like, life. But maybe I was channelling a millennial  ;) (as here).


General Board / Re: Performance problem or what?
« on: August 20, 2018, 09:44:03 am »
If everything is the same bar the AD then it kind of points to that. Maybe the AD is involved in authorising each request to the DB and one AD is slower at responding. Not sure how it all works under the hood but maybe AD is involved in validating security tokens on each request to the DB.  You might be able to find out some kind of message sequence diagram via google to help understand how DB requests and AD interact for authorisation.

Networks can also be set up to give different qualities of services and that might be dependent on which AD users are on.

If you want an approach to problem-solving look up Kepner Tregoe. It helps to work through the logic and isolate the root cause. I've used it a lot over the last 25 years and it was really useful.
Kepner Tregoe - Blast from the past!


Don't under estimate yourself. You are travelling forward into the future one second at a time.

In a block universe that is reference frame dependent.
From, at least, the southern hemisphere.


General Board / Re: Aggregates connector is shown the wrong way around
« on: August 17, 2018, 10:00:44 am »
As explained many times in the past...

In UML 1, it was explicitly stated that aggregations and compositions had the diamonds at the target end. In UML 2, there is no separate metaclass for aggregations and composition; they are associations. Associations are undirected, so the diamond can go on either end.
Indeed so, Neil.  However, just because they can doesn't mean they should! (not a criticism of your post - just extending it)

It is (hopefully obvious) clear that being consistent within the repository (modelling environment) is better than being inconsistent.  Later modelling technologies figured out that it is best to have directional relationships based on client-supplier relationships. For our specific modelling environment, we have standardised on the aggregation kind being specified at the supplier (target, destination) end.  As Simon mentioned, we have adjusted our QuickLinker to facilitate that.

Consistency makes like a WHOLE lot easier!


General Board / Re: Lollipop vs. Interface
« on: August 17, 2018, 09:50:42 am »
That's not a bug. It's intentional Sparx GUI design. Please send complaints to Sirius Cybernetics Co.

You shouldn't use a generic term in a specific context.  You're saying it's not a Sparxian bug, it's a Sparxian GUI Design.
It may well be a bug (from a human point of view) - I'll not comment on that - just the use of language.

It's Friday!   ;) ;)


Pages: 1 2 3 [4] 5 6 ... 415