Topics

106

Bugs and Issues / Change multiple elements

« on: August 09, 2015, 06:11:12 am »

Using Element/Advanced/Change type I can have selected multiple elements. But the change is performed only on one of the selected elements. I faintly remember having ranted about this some time ago. So once again to cool down my anger: rant, rant, rant!

q.

107

Bugs and Issues / Missing features in states

« on: June 10, 2015, 03:27:20 am »

Unlike classes and other elements the properties dialog for states does not have a link to the attributes/operations. You need to use the context menu. EAUI  

q.

108

Bugs and Issues / State machine move operation

« on: June 10, 2015, 02:21:45 am »

When trying to move an operation from one state to another I get "requested move is not supported". Reason for doing it: I want to move an exit operation to the next state and make it an entry. Why shouldn't I be allowed to do that with a simple move?

q.

109

Bugs and Issues / Pasting rich text into notes

« on: March 20, 2013, 03:04:22 am »

I'm on V10. When pasting rich text into class notes I see two effects:
- The original size appears when pasting, but once re-opened the font has the default size
- Leading blanks seem to be stripped off
(FWIW: The paste buffer is filled from my Mac and travels through Parallels into the windoze environment, but that works fine for other applications.)

Anyone seeing the same result?

q.

[edit] The leading blank stripping seems to be an issue with EA/Parallesl paste buffer. When I paste into Wordpad first the leading blanks are preserved. Only when pasting directly into EA they get stripped. However, the size issue is still there.

110

Bugs and Issues / Atrribute/Operation editor

« on: May 13, 2015, 04:29:47 pm »

I wonder who was in charge designing the V12 dialogs. Ctrl-C creates a new entry. Crtl-C is (in even all applications in Windoze) used to copy something to the clipboard. But why be consistent if you can create confusion that easily. And Ctrl-D (instead of being used to duplicate an element instead of Ctrl-C) deletes the line without possibility to undo it. GREAT!

Still (I mentioned that earlier) Ctrl-N does not place the cursor in the name field of the new attr/oper but adds an auto-numbered value. WTF? Does the EA code consist of operation1 to operation999 and attribute1 to attribute999? Most likely, me thinks

q.

111

Bugs and Issues / Bad notes rendering

« on: May 13, 2015, 04:19:35 pm »

In V12 the notes are rendered poorly:

After an "m" there's some extra space. The right border does not have a margin.

I will not report a bug - got tired of that. So this IS my bug report.

q.

112

Bugs and Issues / Insert action pin not working

« on: May 13, 2015, 03:42:07 pm »

I was trying to insert an action pin with V12: Structural Elements/Add. The dialog that popped up asked me to enter a Type but the drop down is empty so I could not create an action pin.

If this is (what I suspect) a bug, it should be fixed. If it's just stupid me, please enlighten me.

q.

113

Bugs and Issues / Inconsistent Feature editing in V12

« on: April 29, 2015, 12:12:45 am »

As with V12 the edit window for attributes/operations has been (inconsistently, how else?) changed.

When I create a new operation from the context for a class I can start typing. Nice. Now I move with Tab to next next input field. Nice too. Now to add a new one I need Ctrl-N (it was discusses and iIRC this is windoze standard?!). Well. Now when I press Ctrl-N the cursor still stays in the current edit field. I need to cursor down and tab backwards. Well, well. Notice the New is located below in case you want to click. The buttons to move/copy have been removed. Is that a good idea?

Now I try to create a new attribute. Typing into the name and tab - ehrm, what? It has created the attribute with the name I typed and now I'm again in the name field for the next attribute. To change type etc I have to cursor down/right. And Ctrl-N again does not take me to the New input field but creates an auto-named attribute where I need to use the cursor (or mouse) to modify it. Unlike for operations the attributes have the New field above the exiting ones. Well, well, well.

In all major companies where I worked there was a test department with almost the same size of the development department. I'm pretty sure Sparx doesn't even have a test department

q.

114

Bugs and Issues / Partitioning an Activity via API

« on: August 21, 2014, 11:10:09 pm »

One of my readers got stuck with my example about partitioning an activity. The code I presented

Code: [Select]

1 part = activity.Partitions.AddNew ("p1", "");
2 part.Size = "90";
3 part.Update ();
4 part = activity.Partitions.AddNew ("p2", "");
5 part.Size = "90";
6 part.Update ();
7 activity.Partitions.Refresh ();
Does not work (he seems to be the first one to get that far )
Now actually there seems to be a buggy behavior Since when you call the Refresh this will annihilate the addition. Instead (since this is one of those inconsistencies in EA) this is a semi-diagram operation: you should call a Repository.SaveDiagram(id) finally. So the Activity/State must be present on the open diagram. Else this method will not work.

Book update is on the way.

q.

115

Bugs and Issues / Bold label

« on: September 30, 2013, 05:59:47 am »

There's an option in the context menu to make a label bold. However, if I check this option I don't see any difference in the rendering. Are my eyes that bad or is that a bug?

N.B. The database has options for underline and italic but the GUI does not seem to offer those options. Because they would not work like bold?

q.

[edit] There seems to be a minor size difference when switching bold. But from pure sight it is not to distinguish! I also tested underline and italics via the API. They definitely are not rendered.

[edit2] Well, it turns out to be a Windoze problem. They never knew much about rendering. If you zoom into the diagram it becomes visible that the font IS bold. Alas, what sense does it make to offer a bold rendering if you can't see it with default settings??

116

Bugs and Issues / ExceptionHandler not taking elements

« on: August 14, 2013, 09:25:49 pm »

If you have an ExceptionHandler to describe an Activity then the handler will accept Actions inside like Activities. But it will refuse Start/Final/Decision (unlike Activity which accepts them inside). Trying to move one of he above into an ExceptionHandler results in a message

The requested move is unsupported

If haven't checked whether UML has some (strange) restriction here, but to me it does not seem to be logical.

Any ideas?

q.

117

Bugs and Issues / Port in sequence diagrams

« on: April 30, 2013, 10:23:47 pm »

In V10 there is a leading slash at ports shown in sequence diagrams. This slash does not appear in 9.3. Is that intentional or a bug?

q.

118

Bugs and Issues / Quick Linker

« on: May 06, 2013, 08:26:30 pm »

I wonder if someone else has the same experience or whether this is just a hick-up with my VM: When you create an element by pressing the space bar on a diagram you see the quick-linker icon (the little arrow), but you can't use it. You need to click once again onto the new element in order to be able to use the quick-linker. For me that is very confusing as often I want to connect the new element with another one. And then the click runs into the void and nothing happens.

q.

119

Bugs and Issues / Ports for Use Cases

« on: April 29, 2013, 09:29:03 pm »

When you open the context menu of a UC in the browser you get an entry "Add/Port". What? I never hear of a use case port?! I tried it - and nothing happened. Well, I thought, one of those things....

Then I opened the context for a UC in the diagram. Here I find "New Element/Port". Well, why should it be named the same way as in the browser? Probably because that would not confuse the user. Okay, I chose that and what did I get? A port! On a use case?!

So what is that. Me being stupid or EA behaving wrong in the one or other menu. And if so, in which of both?

q.

120

Bugs and Issues / Inconsistent behavior with sequence diagrams

« on: May 01, 2013, 03:01:24 am »

If you populate a SD (inside an interaction element) EA behaves habitually inconsistent.

- Drag an actor as instance onto a SD
  -> it appears as stickman with name :<actor>
  -> the browser shows a lifeline symbol in place labeled also :<actor>
- Create an Actor element with the toolbox
  -> it appears as stickman (with no name as we delete that)
  -> now we classify it with our <actor>
  -> the classification is [highlight]NOT[/highlight] shown
  -> the browser shows a stick man also with [highlight]NO[/highlight] classifier
- Drag a class as instance onto the SD
  -> SD looks fine
  -> the browser shows an [highlight]object instead of a lifeline[/highlight]
- Drag a component as instance onto the SD
  -> the SD looks fine
  -> the browser creates an [highlight]object instead of a lifeline[/highlight] and does [highlight]NOT[/highlight] put it inside the interaction
  -> trying to move the instance into the interaction results in a [highlight]The requested move is not supported[/highlight]

Should I report that as bug or simply resign?

q.