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.


Topics - Uffe

Pages: 1 ... 13 14 [15] 16 17 ... 20
211
Bugs and Issues / Truncated attribute initial values
« on: June 20, 2012, 01:12:03 am »
OK, racking my brains here.

I've got some Nodes with Attributes representing domain names, with the name stored in the Initial Value of a typeless attribute named "dns_a".

When shown in a diagram, the initial values get truncated after 15 characters, which is a bit short for most domain names.

Seems like a simple option needs to be set somewhere - but I cannot find a setting for this. Where the blinking flip is it?

Thanks,


/Uffe

212
Bugs and Issues / Include reference data in MDG Technology
« on: June 21, 2012, 04:13:52 pm »
Hi!

I would like to define some project roles and make them available in several projects. These fall into the "reference data" category, and the MDG Technology Creation Wizard does not include an option for them.

Is there a way to include project roles or other reference data in an MDG Technology XML file?

Cheers,

/Uffe

213
Bugs and Issues / SQL search macros not working?
« on: June 19, 2012, 12:00:25 am »
Hey guys,


This seems weird, but...
I can't get the SQL search macros #WC# or #Author# to work.

I've tested on 9.2.921 against a SQL Server repository, and with 9.3.934 on an .EAP file.
In both cases, the construction
Code: [Select]
WHERE Name like '#WC#lass#WC#' fails to return anything, but using the correct wildcard characters (% and *, respectively) returns all "Class1" elements.

Similarly, the construction
Code: [Select]
WHERE Author like '#Author#' returns nothing, but if I substitute the text from the relevant option it works.

I tried using the #Author# macro in a non-SQL search filter - and that works.

Clearly I must be doing something wrong, but I can't see what.
Anyone else spot it?

Thanks,


/Uffe

214
Bugs and Issues / Association Class and Composite Diagram
« on: May 31, 2012, 05:57:01 pm »
Hi!


I've noticed some weird behavior concerning association classes: it seems a class can be either an association class, or be a composite element with its own diagram.

First I create an association class between two other classes.

If I then make the class composite, it is no longer displayed as an association class in the hover tooltip or properties dialog. It retains the reference to the association connector.

If I remove the class from the diagram, then right-click the connector, the "Find Association Class" and "Show Association Class" options are still available.
But if I pick "Show Association Class", EA removes the link between the class and the connector.

If I then place the class in the diagram again an right-click it, I can select Advanced - Association Class and pick the association.
This makes the class non-composite. Its contained diagram is still there.

I've noticed that the NType column in the t_object table switches between 17 for an association class and 8 for a composite one.


Does anyone know of a reason why association classes should not be allowed to be composite?
Or is this simply a bug?

Cheers,


/Uffe

215
Bugs and Issues / Individual model document layouts
« on: May 22, 2012, 01:01:49 am »
Hey chaps and chappettes,


I'm trying to put together a neat-looking master document for a model.
It consists of two model documents, each using its own RTF document template. One dumps all the diagram images and the other creates tables of activities.
I want my diagrams to be in landscape layout, while the tables and the master itself should be portrait.

I can go into my diagram template and change its layout using the File - Printer Setup option. This yields the correct result when I select a package and generate a document with this template.

However, when I generate using the master document, I get all pages in portrait layout, including the ones with the diagram images.
The diagram images shoot off over the right-hand margin, indicating that they honour the selected page layout but the master document does not.

Is there an option I can set somewhere to make the master document generate different page layouts for the different model documents? Or is this a known limitation? (Or bug?)


Cheers,

/Uffe

216
Bugs and Issues / Version control: configure existing package
« on: May 14, 2012, 04:38:12 pm »
Hi!

Situation:
  • A small project (4-6 people), using separate .EAP files and external version control (ClearCase).
  • Container package ("Use Cases") is controlled.
  • Individual packages ("Use Case 001"), directly beneath the container package, are also controlled.
  • The structure has been set up by someone who is no longer with the company. The remaining people are non-power users.
  • Someone has added a new "Use Case 094" and made it controlled in their .EAP file, and checked "Use Cases" back in.
  • After Get All Latest, "Use Case 094" shows up in the others' .EAP files as a package with a single red dot on the left (the bottom icon in the Project Browser Indicators list). It has no contents.
What is the correct procedure to include this in the other users' projects? Is it
1) Refresh the version control repository
2) Package Control -- Get Package?

Just want to make sure before I tell them what to do.


Cheers,

/Uffe

217
Bugs and Issues / Upgrading SQL Server repository
« on: April 25, 2012, 09:34:44 pm »
Hi!

A client is using a hosted SQL Server 2005 for an EA project, and would like to upgrade to SQL Server 2008.
Does anyone here know of any issues with this?

Cheers,


/Uffe

218
Bugs and Issues / Size of sterotyped Port
« on: April 24, 2012, 08:53:21 pm »
Hi all,


Let's say I create a profile with a stereotype <<Blarg>> which applies to Components.
Let's then say I create a non-stereotyped Component "System" and one <<Blarg>> Component "SomeComp".

If I now drop SomeComp onto System and select to create a Port, the Port gets given the <<Blarg>> stereotype. All good -- except the Port is absolutely huge.

Why is this?

I've tried creating a <<blarg>> Port stereotype, with a shape script which only draws a small box. The small box gets drawn, but the bounding box for my Port is still ginormous.

If I don't have the Component stereotype in a profile but simply punch in a string using the keyboard, the Port gets the same non-profile stereotype, and is the right size.

Anyone recognize this?
Any way to work around it?
I'm on 9.2.921.


Cheers,


/Uffe

219
Bugs and Issues / Show level numbering in diagram
« on: April 10, 2012, 07:59:00 pm »
Hi all,

I can switch on Level Numbering on a package in the project browser, and get EA to print the numbers in a document template.

Is there a way to switch on display of level numbers in diagrams? Can't seem to find one...

Cheers,


/Uffe

220
Bugs and Issues / Project access for EALite
« on: March 22, 2012, 11:50:35 pm »
Hey guys,

Does anyone know the rules regarding project access for EALite?
I'm looking at rolling out EALite on dozens of common-use PCs at a customer site (in meeting rooms, that sort of thing), but then of course information security becomes an issue.

EALite doesn't log in to the project (right?) so there's no need for an in-project user account.
But does the user running EALite need database access permission?

If the answer is no, is there any way I can restrict project access for EALite?

Cheers,


/Uffe

221
Bugs and Issues / Override Common toolbox
« on: March 12, 2012, 06:37:03 pm »
Hi!

I'm trying to put together an MDG Technology where I want to get rid of all proper model elements and connectors (eg artifact, information flow) from the Common toolbox, leaving only diagram objects.

I can create the toolbox OK, but I can't remove the Common one.
There are two problems I'm running into.

1) Overriding default toolboxes, as described in the help file, doesn't seem to work. I have tried overriding the Class toolbox in the manner described, but the default toolbox still opens up in all Class diagrams (old and new).

2) The help file's list of EA toolboxes does not include the Common toolbox. Does that mean the Common toolbox can't be overridden?

Cheers,


/Uffe

222
Bugs and Issues / Floating diagrams: strange focus behaviour
« on: March 13, 2012, 01:36:55 am »
Hi all,

The floating diagrams introduced in 9.3.930 are great, but the focus behaviour is a little confusing.
Clicking and/or dragging the top bar of a floating diagram does not bring it into focus for things like the diagram toolbox or the diagram toolbar. You have to click inside the diagram area itself for that.

I would like the focus to change when I click the window bar. As it is, the floating diagram looks as if it has focus (darker window bar) when it doesn't. I'm reporting this as a bug.

223
Bugs and Issues / Activity parameters & invocation action arguments
« on: February 22, 2012, 12:10:14 am »
Hi!


I can create parameters on my activities, which allow me to specify arguments when I use those activities to create invocation actions. Fine.

But while I can specify a type for my parameter, eg a specific class, I do not seem to be able to specify an instance of that class as the value - there's no ellipsis button.

Is there a way to achieve this? In other words, is there a way to select, rather than type in, the value of an action parameter?

Cheers,


/Uffe

224
Bugs and Issues / Activity simulation: input and arguments
« on: February 22, 2012, 12:17:45 am »
Hi!


I'm fiddling about with some model simulation.

Invocation actions are executed correctly, ie they cause the defining activity (classifier) to be run through the simulation.

Is there a way to display the parameter values as set on the invocation action?
If not, is there another way to achieve the same sort of thing, possibly using different model elements?

Also, I am able to specify an input for the simulation, but that doesn't seem to do anything. Is the input used for anything and is there a way to display it during the simulation?

Cheers,


/Uffe

225
Bugs and Issues / Read-Only package: how?
« on: February 15, 2012, 12:07:07 am »
Hey all,

I was just flipping idly through the version history, and came across a reference to making packages read-only, introduced in 9.0 (909). Sounds great - except I can't seem to find how to set this property.

It's not in the package's general properties nor in the advanced properties, I don't see it in the Properties window nor is there a tagged value for it, and I can't find an option for it in any context menu.
Searching through the help file, weeeelll... that just gets you a lot of hits in the automation section.
So.

I know I'm being a complete dunce here, but please - how do I set a package read-only?

Cheers,


/Uffe

Pages: 1 ... 13 14 [15] 16 17 ... 20